| name | pr-ready |
| description | Pre-pull-request checklist — verify the code works, the diff is reviewable, and the PR carries context and evidence of testing. Run before opening any pull request. |
PR readiness check
Never inflict unreviewed code on collaborators. Opening a PR you haven't
verified yourself delegates your work to the reviewer — they could have prompted
an agent themselves. The initial review pass is our responsibility.
Work through this checklist and report the result of each item. Do not open the
PR until every item passes.
Checklist
- The code works, provably. Full test suite green (
test-runner subagent)
AND manually exercised (/manual-test). "The tests pass" alone is not
sufficient.
- Self-review done. Run the
code-reviewer subagent on the diff and
address or consciously accept every finding.
- The diff is reviewable. Small enough to review without heavy cognitive
load. If it's grown too big, split it: several small PRs beat one big one,
and rearranging commits is cheap (
/git-rescue).
- Commits tell a clean story. Squash fixups, reword vague messages.
- The description carries context. What higher-level goal does this serve?
Link relevant issues/specs. Then read the description yourself — it's rude
to ask someone to read text you haven't read.
- Evidence included. Notes on how it was manually tested — a showboat
document from
notes/, screenshots, or a demo recording. Show the reviewer
their time won't be wasted.