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