Peer QA Review (Round 1)

A teammate has marked work as ready for QA. Your job: verify it before it goes to customer acceptance / QA2 / internal close. Round-1 QA is not rubber-stamping — re-run verification yourself, check formal correctness, check inventory and docs, post a structured QA comment, transition the ticket.

When this skill applies

Auto-trigger:

• Ticket transitioned to QA status (or equivalent: "Review", "Code Review", "Ready for Review")
• Comment "ready for QA" / "ready for review" posted by the implementer
• User asks for "IT QA review", "internal QA", "peer review", "quality gate", "review and resolve"

Skip when:

• Ticket is still In Progress — ask implementer to transition first
• Ticket is QA2 / customer-acceptance — different scope
• Ticket is already closed — post-mortem only; say so explicitly
• You are also the implementer — you can't self-review (see references/edge-cases.md)

Companion skills