Ready for Review
Use to package a change before requesting/receiving review.
Steps
- •Summarize
- •What changed and why (1-3 bullets)
- •Risk and impact
- •Note user-facing or operational risks; call out migrations/rollouts
- •Tests
- •List commands run and results; note unrun/blocked tests
- •Files touched
- •Highlight key files and sensitive areas
- •Follow-ups
- •TODOs, flags to remove, monitoring to check post-merge
- •Next action
- •If ready, trigger requesting-code-review skill; otherwise keep local
Outputs
- •Short review bundle: summary, risks, tests, files, follow-ups
When to stop and ask
- •If critical tests cannot run or results are unclear
- •If risk is high and needs a deeper plan