/review loads the code-reviewer agent to run a structured review of the implementation against the plan, requirements, and quality standards. It is the gate between /implement and /git — nothing ships without a review verdict.
What gets reviewed
The review covers four areas. Each one is checked independently and reported separately.Plan compliance
- Does the implementation match what was planned?
- Are all acceptance criteria met?
- Is there any scope creep — things added that weren’t planned?
Code quality
- Is the code readable without needing comments to explain it?
- Are functions doing one thing?
- Is error handling present at system boundaries?
- Are there tests for the new behavior?
Security
- Is there any user input that isn’t validated?
- Are there any secrets or credentials in the code?
- Are there any new endpoints missing authorization?
Performance
- Any N+1 queries — a loop containing a database call?
- Any synchronous blocking I/O in an async context?
- Any unbounded data fetching — missing
LIMITon queries? - Any unnecessary re-computation inside loops?
Issue severity
Only Critical and High issues block the gate. Medium and Low issues are surfaced as suggestions and can be addressed after shipping.
Review output format
The code-reviewer agent produces a structured report:Verdicts and what they mean
- APPROVED
- APPROVED WITH SUGGESTIONS
- CHANGES REQUIRED
No issues found. The implementation is ready to ship. The gate to
/git is open.Agents involved
The receiving-code-review skill is also loaded when applying feedback from a CHANGES REQUIRED verdict, to ensure feedback is incorporated correctly.
If the review returns CHANGES REQUIRED, SuperAntigravity loads the receiving-code-review skill to guide you through applying the feedback systematically. After fixes are applied,
/review is run again before the gate opens.