workflow-step-summaries
Write clear GitHub Actions step summaries with progressive disclosure.
- License 许可
- MIT
- 所属仓库
- github/gh-aw
- 最近更新
- 2026-11-15
- Stars
- ★ 5.6k
- Forks
- 626
01 前言 Front Matter
- name
- workflow-step-summaries
- description
- Write clear GitHub Actions step summaries with progressive disclosure.
02 资源文件 13
- 参考文档references/examples.md3.2 KB
- 参考文档references/model-selection.md3.0 KB
- 参考文档references/setup.md3.0 KB
- 参考文档references/task-schema.json5.7 KB
- 参考文档references/telemetry-contract.md4.4 KB
- 脚本scripts/lib/common.mjs1.8 KB
- 脚本scripts/lib/model-selection.mjs3.5 KB
- 脚本scripts/lib/ollama-adapter.mjs10.5 KB
- 脚本scripts/lib/pudu-adapter.mjs4.7 KB
- 脚本scripts/lib/report.mjs4.6 KB
- 脚本scripts/lib/task-store.mjs8.4 KB
- 脚本scripts/lib/telemetry.mjs3.0 KB
- 脚本scripts/pudu-task.mjs12.7 KB
03 SKILL.md 正文
GitHub Actions Step Summary Guidance
Use this skill when generating content for $GITHUB_STEP_SUMMARY.
Structure summaries for quick scanning
- Start sections at
###(h3) for readable hierarchy in workflow run pages. - Keep titles plain text with no emojis.
- Put the most important status and outcomes first.
Use progressive disclosure
- Wrap detailed diagnostics, logs, and secondary data in HTML
<details>blocks. - Use a concise
<summary>line that states what the collapsed section contains. - Keep default-expanded content short; move verbose output into collapsible blocks.
Use Markdown for code and review output
- In
actions/github-script, prefercore.summary.*helpers to build summary content. - Use inline code with backticks for commands, paths, IDs, and config keys.
- Use fenced code blocks with a language tag for logs, diffs, snippets, or commands.
- Present review findings as markdown sections with clear severity and action items.
Suggested checklist before writing
- Confirm section headings start at h3.
- Confirm no title includes emoji.
- Confirm verbose content is inside
<details>blocks. - Confirm code and review content uses proper markdown code formatting.
04 同仓库更多 Skills
cracktro
Edit, preview, and verify the standalone interactive talk deck in docs/public/cracktro (slides, SVG diagrams, transitions, WebAudio sound).
create-connector
Create or extend a declaration-only third-party connector, with narrow reads, separate safe outputs, optional protected triggers, and offline conformance evidence.
GitHub Agentic Workflows
GitHub Agentic Workflows (`gh-aw`) is a GitHub CLI extension for writing Agentic Workflows in markdown and compiling them to GitHub Actions.
windows-compatibility
Cross-platform path handling and command patterns
versioning-policy
Semver versioning rules for Squad SDK and CLI — prevents prerelease version incidents
tiered-memory
Three-tier agent memory model (hot/cold/wiki) for context reduction per spawn