afc:review

/afc:review — Code Review

Performs a comprehensive review of changed code (quality, security, performance, architecture compliance). Validates completeness of the review itself with convergence-based Critic Loop.

Arguments

• $ARGUMENTS — (optional) Review scope (file path, PR number, or "staged")
  • If not specified: full git diff of current branch (unstaged + staged)

Project Config (auto-loaded)

!cat .claude/afc.config.md 2>/dev/null || echo "[CONFIG NOT FOUND] .claude/afc.config.md not found. Create it with /afc:init."

Config Load

Always read .claude/afc.config.md first — needed for CI Commands (YAML). Architecture, Code Style, and Project Context are auto-loaded via .claude/rules/afc-project.md.

If config file is missing:

1. Ask: ".claude/afc.config.md not found. Run /afc:init?"
2. If user accepts → run /afc:init, then restart with original $ARGUMENTS
3. If user declines → abort

Execution Steps

1. Collect Review Targets

1. Determine scope:
   • $ARGUMENTS = file path → that file only
   • $ARGUMENTS = PR number → gh pr diff {number}
   • $ARGUMENTS = "staged" → git diff --cached
   • Not specified → git diff HEAD
2. Extract changed file list; read full content of each file (not just the diff)
3. Load spec context (if available): .claude/afc/specs/{feature}/context.md and spec.md. If neither exists, skip SPEC_ALIGNMENT with note "no spec artifacts available"
4. Build Impact Map — see Reverse Impact Analysis

2. Parallel Review (scaled by file count)

Assess complexity holistically: total diff size, file complexity, change diversity, and whether changes are localized or cross-cutting.

Pre-scan for parallel batch / swarm: Before distributing files, collect cross-boundary context — outbound calls between changed files with function signature + 1-line side-effect summary. Include Impact Map. Provide each agent a ## Cross-File Context block. Skip pre-scan for Direct mode.