← ClaudeAtlas

pr-test-planlisted

Analyze one or more pull requests, map every code change to the existing and new functionality it touches (including cross-repo, mirrored-route and shipped-client blast radius), and produce a manual click-through QA test plan with numbered steps, expected results, and traceability back to the diff. Use when asked "what do I need to test for this PR", to build a QA or regression plan for a PR/branch, to assess the blast radius or impact of changes, or to prepare a manual test pass before merging.
the-Sreejith/claude-pr-test-plan · ★ 0 · Testing & QA · score 67
Install: claude install-skill the-Sreejith/claude-pr-test-plan
# PR Test Plan Turn a PR (or a set of related PRs across repos) into a **manual click-through test plan** a human can execute without reading the diff. Two questions drive everything: 1. **What is new?** — functionality that did not exist before and has never been exercised. 2. **What is now different?** — functionality that already existed, shipped, and could regress because this diff reached it. Question 2 is where releases break, so it gets equal weight. A plan that only tests the feature is a failed plan. ## Hard rules - **Read-only against the repos.** Never `git checkout`, `git stash`, `git add`, `git pull`, or switch branches — other sessions may hold uncommitted work in the same tree. Use `gh pr diff` and read files in place. - **Every test case cites the change that motivates it** (`repo/path/file.ts` plus a line or commit). No citation = you invented it, delete it. - **Every changed file lands somewhere**: in a test case, or in the "no user-visible surface" list with a one-line reason. This is the completion check. - **Never claim a surface was verified.** This skill produces a plan for a human. It does not run the flows. - Steps are clicks and screens, not code. "Open Settings → Billing, click **Add card**" — never "call `createPaymentMethod`". ## Step 1 — Collect the PRs Accept one or more PR URLs, `owner/repo#N`, or "the current branch". If PRs from several repos are given, they are **one feature**: produce **one** merged plan, not N plans. Ask only if no