What problem does it solve? Pull requests often ship without a concrete, human-verifiable checklist, leaving reviewers to guess how to validate a change. This Skill derives a manual QA checklist from the branch's plan, PR summary, or commits and writes it into the PR body as a ## QA Checklist section, complete with a table classifying each step's automatability and test coverage. ## Core Features & Use Cases - Checklist derivation: Builds concrete, user-visible verification steps from the plan under docs/plans/, the PR body Summary, or commit history — not generic advice like "run the tests". - Automatability classification: Emits a slug-keyed table marking each item as unit, integration, e2e, or manual-only, plus whether a backing test already exists, surfacing coverage gaps before merge. - Idempotent PR body updates: Pulls the live PR body via scripts/pr-body.py, edits only the QA section (recognizing legacy ## Manual QA and ## Test plan headings), and pushes it back without touching anything else. - Use Case: After implementing a streaming chat feature on a branch, run /qa-checklist to insert steps like "open the chat page, send a prompt, confirm the reply streams in" into the PR, with a table flagging that the streaming path lacks an e2e test. ## Quick Start Run /qa-checklist on the current branch to generate a manual QA checklist and write it into the open PR's body.
