/rota-review
Review a branch against its spec and conventions before it leaves.
When to use
Use on “review this”, “check before I ship”, “look over the branch”, before a merge or PR, or implicitly from /rota-ship.
Reach for another skill when
- you need evidence the built product works (perf, a11y, smoke), not a read of the diff:
/rota-qa - you want code changed based on findings rather than a verdict:
/rota-refactor - the code is still in flight:
/rota-work
/rota-review
Spec reviewer: B03 promised --limit 0 yields zero rows; cmd/list.go and TestListLimitZero match. Standards reviewer: conventions and test quality fine. Verdict: PASS (the worse of the two)
- nothing in the tree (read-only, no commits)
- spec and quality verdicts recorded against the reviewed sha
Flags and modes
--since <sha>- re-review a bounced branch, only the fix, against the last review’s findings
--queue- issue backend; review every needs-review item’s open PR or MR and merge the ones that pass
Details
Staff-engineer review of a feature branch before it leaves your machine: scopes the diff, pulls relevant KNOWLEDGE.md topics and returns PASS / CONCERNS / FAIL with file-and-line evidence. Read-only: no mutations, no commits. On the issue backend, --queue instead works through every needs-review item’s open PR or MR and merges the ones that pass. See review and ship for the full flow.