What problem does it solve? QA teams often receive vague handoffs after a feature branch is finished, forcing testers to read code or PRs to figure out what to verify. This Skill analyzes the branch's own changes and produces a self-contained qa_checklist.md with concrete, screen-verifiable test cases. ## Core Features & Use Cases - Three-dot diff analysis: Compares the branch against the merge-base with develop so only the branch's own changes are considered, avoiding flows from unrelated merged work. - Structured test matrices: Maps direct flows into tables covering happy path, edge cases, and negative cases, plus a regression section for components sharing modified types or utilities. - Environment preconditions: Detects new environment variables and feature flags so QA can configure the test environment before starting. - Use Case: After finishing a feature branch that modifies a selection component and adds a validation guard, run this Skill to produce qa_checklist.md with per-flow test tables and regression smoketest suggestions ready to hand to the QA team. ## Quick Start Ask the agent to generate the QA checklist for the current branch against develop and write it to qa_checklist.md.