Auto QA Scenarios Translate a window of merged pull requests into a practical manual verification plan a human tester can follow: PRs grouped into a handful of testing areas, a recommended testing order, and per area where to click , what to verify , and what can go wrong , with a full PR-by-PR appendix for traceability. The deliverable is two self-contained artifacts (markdown + HTML) under , landed as a docs-only PR. This skill owns the analysis and the report. Everything PR-shaped — claim, worktree, branch, execution plan, validation gate, labels, review pass, summary comment, resume — is…