What problem does it solve?
GitHub Actions step summaries often become unreadable walls of text, mixing critical status with verbose logs. This Skill provides clear authoring rules so summaries written to $GITHUB_STEP_SUMMARY are scannable, well-structured, and easy to review in workflow run pages.
Core Features & Use Cases
- Structured Hierarchy: Enforces h3-level section headings, plain-text titles without emojis, and status-first ordering for quick scanning.
- Progressive Disclosure: Guides wrapping verbose logs and diagnostics in HTML <details> blocks with concise <summary> lines.
- Markdown Formatting Rules: Covers use of core.summary.* helpers in actions/github-script, inline code for paths and IDs, and fenced code blocks for logs and diffs.
- Use Case: When an agentic workflow posts CI failure investigation results or PR review findings to a step summary, apply this Skill so reviewers see key outcomes first and expand details only when needed.
Quick Start
Use the workflow-step-summaries skill to write a step summary for this workflow run following the heading, disclosure, and markdown formatting guidelines.
