Review Agent

Role: worker. This skill performs the actual review using the agent
definition as its specification.

You have been invoked with the /review-agent skill. Run a single named review agent.

Worker constraints

1. Follow the agent definition exactly. The agent file is your
   specification — detect what it says to detect, skip what it says
   to skip.
2. Respect context needs. When --changed or --since is used,
   honor the agent's Context needs field (diff-only, full-file, or
   project-structure).
3. Do not add findings beyond the agent's scope. If the agent
   says "Ignore: naming, tests" — do not flag naming or test issues.
4. Return structured JSON only. Output the standard result
   format. Do not add prose commentary.
5. Be concise. Issue messages should be one sentence. Suggested
   fixes should be actionable, not explanatory. No preambles or
   filler.

Parse Arguments

Arguments: $ARGUMENTS

Required: agent name ($0, e.g., test-review, js-fp-review, security-review)

Optional:

• --changed: Review only uncommitted changes
• --since <ref>: Review files changed since a git ref
• --path <dir>: Target directory (default: current working directory)

Steps

1. Load agent definition

Read agents/<name>.md. If the file doesn't exist, list available
agents from agents/ and ask the user to pick one.

2. Determine target files

Same logic as /code-review:

• --changed: git diff --name-only + git diff --cached --name-only
• --since <ref>: git diff --name-only <ref>...HEAD
• Default: glob all source files

3. Run review

Follow the agent definition to review each target file. Produce a JSON result:

{
  "agentName": "<name>",
  "status": "pass|warn|fail",
  "issues": [
    {
      "severity": "error|warning|suggestion",
      "file": "<path>",
      "line": 0,
      "message": "<description>",
      "suggestedFix": "<fix>"
    }
  ],
  "summary": "<summary>"
}

4. Report

Display the result as a formatted summary with issues grouped by file. Include suggested fixes inline.