skills/code-review/SKILL.md
Multi-agent code review with parallel specialized reviewers, architecture validation, and challenge validation. Use `rq` to request a review of diffs (defaults to main branch), `rs` to respond to review findings. Triggers on "review this", "review my code", "code review", "check for bugs", "audit this", when examining PRs, pull requests, branches, or diffs. Always asks user before applying fixes.
npx skillsauth add martinffx/claude-code-atelier code-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Multi-agent code analysis with parallel reviewers and challenge validation.
Uses explicit subagent dispatch patterns from code-subagents.
| Invocation | Behavior |
|------------|----------|
| (no arguments) | Review diff to main branch |
| rq | Review diff to main branch |
| rq main | Review diff to main branch |
| rq develop | Review diff to develop branch |
| feat/foo | Review diff to feat/foo (bare branch = rq) |
| rs | Respond to review findings (interview mode) |
| Step | Subagent | Uses | Parallel | Purpose |
|------|----------|------|----------|---------|
| 1 | Triage | scout agent | No | Detect context, select reviewers, identify skills to load |
| 2 | Reviewers | general subagent | Yes (per reviewer) | Specialty analysis (loads detected skills) |
| 3 | Synthesis | general subagent | No | Deduplicate findings |
| 4 | Architect | architect agent | No | Architecture review |
| 5 | Challenge | oracle agent | No | Validate findings with sequential-thinking |
No subagents. Interactive interview mode — see rs.md.
Follows code-subagents patterns:
| Agent | Used In Step |
|-------|--------------|
| scout | Triage (context retrieval, file analysis) |
| architect | Architect (architecture review) |
| oracle | Challenge (validate findings, sequential-thinking) |
| general | Reviewers, Synthesis |
See agents/ for agent definitions.
| Reference | Purpose | |-----------|---------| | rq.md | Request review workflow - detailed steps with prompts | | rs.md | Respond to review workflow - interview mode | | reviewers.md | Reviewer definitions and prompts | | output.md | Output format specification |
rq, or bare branch → rq.mdrs → rs.mddevelopment
Security architecture and threat modeling knowledge. Auto-invokes when designing features that handle untrusted data, authentication, authorization, external integrations, file uploads, or sensitive data. Provides risk assessment frameworks, trust boundary analysis, and security design principles — not implementation code.
testing
Adversarial review of non-trivial decisions using fresh-context scrutiny. Use when correctness matters more than speed, when stakes are high (production, security-sensitive logic, irreversible operations), or before committing significant architectural or implementation choices.
development
Compact the current conversation into a handoff document for another agent to pick up.
testing
Socratic interrogation of plans against the project's domain model and documented decisions. Use when the user wants to stress-test a plan, clarify terminology, or validate assumptions against existing domain language. Updates CONTEXT.md and ADRs inline as decisions crystallise.