Structure agent output summaries in Claude Code
Use a consistent report for status, summary, findings, the immediate next action, and a spec changelog entry.
中文Install in Claude Code
A Claude Code workflow with the agent name, spec ID, date, validation stage, and actual findings available.
- Review `.claude/skills/summarize-output/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.claude/skills/summarize-output/` in your project and save the reviewed file as `.claude/skills/summarize-output/SKILL.md`.
- Start Claude Code from that project's root, then select `/summarize-output` in the slash menu.
Example task
The agent is proof-reader for SPEC-17 on 2026-07-09 during review. The cover line is cover-4. The preview table is correct but the explanation cites an outdated filename, so the review cannot pass as written.What to check
Keep SPEC-17 and 2026-07-09 in the report header. Record `status=WARN; finding=stale filename at cover-4; next=verify filename`. Include the problem in the summary, its location in the findings, and one entry for the spec changelog.
Original SKILL.md on GitHub · Updated
Frequently asked question
How does an agent review report make the next action clear?
Record the status and blocker, give findings with severity and location, then name one immediate action and log its related change in the spec.