/code-review
/code-review — Operator-driven per-file code-quality review pass across src/, scripts/, and tools/.
Role: Reviewer Pipeline position: fortress
Operator-driven per-file code-quality review pass across src/, scripts/, and tools/.
Canonical invocation
/code-reviewWith arguments:
/code-review [path/to/plan-suite/] [phase-id] [--dry-run]Inputs
Host repository at any lifecycle state
Outputs
Per-file findings + disposition log in REPORT.md
Downstream
The line-by-line review stage of the Audit Review Sequence
Workflow phases
The command follows the standard /plan pipeline workflow:
- Load context — Read plan suite, rules, and Resumption Contract.
- Verify prerequisites — Confirm dependency phases complete.
- Execute tasks — Perform the command mission.
- Verify outputs — Confirm all declared outputs exist and pass quality gates.
- Update PROGRESS.md — Record verified outputs in the Phase Output Registry.
- Emit REPORT.md — Pre-emission gate release proof recorded.
Failure modes
| Symptom | Cause | Recovery |
|---|---|---|
| Prerequisite incomplete | Dependent phase not finished | Complete upstream phase first |
| Quality gate FAIL | Output does not meet standards | Fix the output and re-run |
| Missing input file | Plan suite file absent | Run /plan-generate to create it |
Examples
# Dry-run to preview what would happen
/code-review --dry-run
# Execute against a named plan suite
/code-review path/to/plan-suite/Cross-references
/research-disseminate
/research-disseminate — Drives post-acceptance dissemination and impact: preprint announcement, public artifacts, FAIR archival deposit, altmetrics tracking, the reviewer rebuttal / revision loop, and the registered-report stage-2 path — the terminal stage of the /research pipeline, after /research-publish.
/code-audit
/code-audit — Cross-file forensic code audit at repository-corpus scope.