pr-reviewlisted

# PR Review ## When to use Use this skill on every PR before merge, or when the user asks "review my changes". ## Steps 1. Read the full diff and the linked issue or context. 2. Check correctness: off-by-one, null handling, concurrency, error paths. 3. Check security: input validation, authz, secrets, unsafe deserialization. 4. Check coverage: are the changed behaviours tested? Add suggested tests. 5. Check style and clarity, but only when it affects maintainability. 6. Return a prioritized list: must-fix, should-fix, nit. ## Examples - "Review this PR for correctness and missing tests" - "What could break in this diff?" ## References Separate blocking issues from nits; quote the exact lines and give a concrete fix, not just a complaint.