| name | pr-gates |
| description | This skill should be used when the user asks to "open a PR", "prepare for review", "address review comments", "run gates", or "verify before pushing" in this repository. Enforces preflight/gate workflow, migration safety, and review-evidence closure. |
PR Gates
Mandatory Flow
- Run
just preflight before finalizing changes.
- Run
just gate-pr before pushing or updating a PR.
- If the same command fails twice in one session, stop rerunning and switch to root-cause debugging.
- Do not push when any gate is red.
Review Feedback Closure
For every P1/P2 review finding, include all three:
- Code change reference (file path and concise rationale)
- Targeted verification command
- Pass/fail evidence from that command
Async And Stateful Changes
When touching worker lifecycle, cancellation, retries, state transitions, or caches:
- Document terminal states and allowed transitions.
- Explicitly reason about race windows and idempotency.
- Run targeted tests in addition to broad gate runs.
- Capture the exact command proving the behavior.
Migration Safety
- Never edit an existing file in
migrations/.
- Add a new timestamped migration for every schema change.
- If a gate flags migration edits, stop and create a new migration file.
Handoff Format
- Summary
- Changed files
- Gate commands executed
- P1/P2 finding-to-evidence mapping
- Residual risk
Coding Discipline
- See
.claude/rules/coding-discipline.md. Before push, confirm every changed line traces to the request (surgical changes). If TDD was skipped, the exception must be named in the PR summary.
