// Generate a compact summary of the most recent code review results and save it for future sessions. Use this at the end of a coding session after /code-review has run, or when the user says "summarize the review", "save the results", "generate a summary", or wants to preserve review context before closing a session.
Scaffold a new review agent from a description or URL. Use this whenever the user wants to add a new review agent, detect a new category of code issue, or says things like "add an agent for X", "create a reviewer for Y", "I want to check for Z in code reviews". Also use when given a URL to a coding standard or best-practices guide that should become a review agent.
Install a Claude Code plugin and register it in plugins.json so the full team can replicate the install. Use this whenever adding a new plugin to the project — it keeps plugins.json in sync with what is actually installed.
Apply correction prompts generated by /code-review. Use this whenever the user wants to apply, fix, or action the results of a code review — phrases like "apply the fixes", "fix the issues", "apply corrections", or after /code-review has run and produced a corrections/ directory.
Run all enabled review agents against target files. Use this whenever the user asks for a code review, wants feedback on their code, says "review my code", "check this before I PR", "what's wrong with this", "run the agents", or has just finished implementing a feature. Use proactively before commits and pull requests.
Audit code-review agents, skills, and hooks for structural compliance. Use this when adding or modifying any agent, skill, or hook file, or for a periodic health check of the toolkit. Trigger phrases: "audit the agents", "check compliance", "validate the skills", "are the agents correct", or any time agent/skill files change.
Run eval fixtures against review agents and grade results. Use this after adding or modifying a review agent, to validate detection accuracy, or when the user says "run the evals", "test the agents", "check for regressions", or "how accurate is the agent".
| name | review-summary |
| description | Generate a compact summary of the most recent code review results and save it for future sessions. Use this at the end of a coding session after /code-review has run, or when the user says "summarize the review", "save the results", "generate a summary", or wants to preserve review context before closing a session. |
| argument-hint | [--from <json-file>] |
| user-invocable | true |
| allowed-tools | Read, Write, Glob, Bash(date *), Bash(git rev-parse *), Bash(git branch *), Bash(mkdir *) |
Role: orchestrator. This skill summarizes and persists review results — it does not review code.
You have been invoked with the /review-summary skill. Generate a compact summary of the most recent code review.
Arguments: $ARGUMENTS
--from <json-file>: Read review results from a JSON file (output
of /code-review --json). If not provided, summarize from the
most recent /code-review output in the conversation.If --from is specified, read the JSON file. Otherwise, look for
the most recent code review results in the current conversation
context.
Extract: overall status, agent statuses, issue counts by severity, and top issues.
Write a summary under 150 words following this template:
## Review: <branch> @ <short-sha> — <date>
**Status**: <PASS|WARN|FAIL> (<N> agents, <N> issues)
**Findings**:
- <top 3-5 findings, one line each, severity prefix>
**Blocked by**: <agent names that returned fail, or "none">
**Action items**: <1-3 concrete next steps>
Write the summary to .claude/review-summaries/<date>-<short-sha>.md.
Create the .claude/review-summaries/ directory if it doesn't exist.
Display the summary to the user. Note that it will be available as context in future sessions.