Conduct full post-implementation code review
review-codecommandsetup L2★0
joecrotchett/spec-driven-claude ↗What it does
Post-implementation code review per FOAA architecture rules
Best for
Verify post-implementation code complies with FOAA architecture (dependency direction, module structure, security) without guessing.
Inputs
- · Changed files (from git diff or conversation context)
Outputs
- · Review report with PASS/VIOLATION/N/A for 11 rules
- · Security findings
- · Refactoring recommendations
Requires
- · git (diff, status)
- · Read tool for file inspection
Preconditions
- · Git repo or conversation history available
- · Files readable
- · FOAA rules defined (Part 1-3)
Failure modes
- · Git command fails
- · File read permission denied
- · Changed files list incomplete
- · Rule interpretation ambiguous
Trust signals
- · 11 explicit architecture rules with cite-the-line verification
- · Security checklist
- · Real-code reading (not assumptions)