code-review

# Code Review Skill Multi-agent code analysis with a simplicity gate, focused reviewers, and challenge validation. Uses explicit subagent dispatch patterns from [code-subagents](../code-subagents/SKILL.md). ## Prerequisites - **Required**: git ## Arguments ### Command Routing | 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) | ## Subagent Architecture Use these concrete harness subagent types. If an exact match is unavailable, use the most correct available subagent based on the harness-provided descriptions. | `subagent_type` | Purpose | |-----------------|---------| | `sentinel` | Triage only: changed-file analysis, context retrieval, reviewer selection | | `oracle` | Reviewer personas, evidence-based critique, failure-mode analysis, challenge validation | | `architect` | Architecture, design-boundary, data-model, and API-contract review | Reviewer names such as `Security`, `Correctness`, `Maintainability`, and `PerformanceOperator` are prompt personas, not subagent types. Do not use `general`; it is not a harness agent. `Simplicity` is a mandatory reviewer persona for migrations, refactors, and architectural changes. Run it before the other reviewers; do not include it in...