A tool that reads a pull request's code changes and proposes the unit, integration, end-to-end, and chatbot tests that should cover them. A pull request is a proposed change submitted for review before it is merged.

Use it after a pull request opens or before review to create or improve a concrete test plan.

It helps catch missing tests by connecting each changed file and its risk to the behaviors that need checking.

test-plan — Skill for Claude Code by GuitarAlchemist

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add GuitarAlchemist/ga --skill test-plan

Clone the repo

git clone --depth 1 https://github.com/GuitarAlchemist/ga

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/guitaralchemist/ga/test-plan/github.svg)](https://agentmods.dev/skills/guitaralchemist/ga/test-plan)

Your own site

<a href="https://agentmods.dev/skills/guitaralchemist/ga/test-plan"><img src="https://agentmods.dev/badge/skills/guitaralchemist/ga/test-plan/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/guitaralchemist/ga/test-plan"><img src="https://agentmods.dev/badge/skills/guitaralchemist/ga/test-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 115 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,714 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00115	$0.04714
Opus 5	$0.00057	$0.02357
Sonnet 5	$0.00023	$0.00943
Haiku 4.5	$0.00012	$0.00471

Measured 9d ago against content hash 71fcf678f1a3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

test-plan scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

| `ReactComponents/ga-react-components/vite.config.ts` | Vite middleware | integration (curl the endpoint in dev mode) |

.claude/skills/test-plan/SKILL.md · 397 lines

How it starts

The opening of the file, as written. The whole thing — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/test-plan

Closes the "developer forgot to write a test plan" gap. Reads a PR diff, maps each changed file to its likely test surface, and emits a structured set of test cases the author (human or agent) should add before merge.

Invoked as /test-plan for the current branch's open PR, or /test-plan <PR#> for a specific number.

Sister skills:

/grade-last-pr — post-merge intent-vs-delivery (looks backward).
/council — pre-merge gate for one-way doors (escalated review).
/test-plan — pre-merge test-coverage proposer (this skill; daily use).

Together they form the before / during / after triangle of PR quality.

When to run

Right after a PR opens — the .github/workflows/test-plan-suggester.yml fires automatically on opened + synchronize if the PR body lacks a ## Test plan section. Re-runs on every push to update the proposal.
Before requesting review — if you wrote a thin ## Test plan and want a second opinion on what else to test.
When grading an agent-authored PR low for coverage — re-run after the agent fixes its plan, before merging.

Do NOT invoke for:

Typo PRs (< 5 changed lines, no logic change) — overhead exceeds value.
Pure-documentation PRs (only *.md outside tests/docs/contracts) — no test surface.
Revert PRs — the test plan is "the prior PR's test plan, rerun" (use /grade-last-pr on the revert instead).
Unmerged PRs you're about to abandon — wasted budget.

What this skill does NOT do

Never auto-writes test code. Writing tests requires understanding intent, fixture layout, and the team's test style — that's an engineering call, not a heuristic. A future /test-write skill could take the proposal as input; this skill stops at the proposal.
Never blocks merge. The workflow posts a comment; it is advisory. The blocking gate for one-way doors is /council. For routine PRs, the review process is the gate.
Never edits the PR body. Adds a sticky comment with marker . The author owns the body; the bot owns the comment.

Read the full file on GitHub · 397 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

9d ago First seen · 397 lines · 115 tokens per session scan A 71fcf678f1a3

Subscribe to this mod's changes

test-plan is a skill published in the GitHub repository GuitarAlchemist/ga (2 stars, last pushed today), licensed MIT. It adds 115 tokens to every session and 4,714 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

E2E testing Testing Unit testing

axiom-testing

Use when writing ANY test, debugging flaky tests, making tests faster, or choosing Swift Testing vs XCTest. Covers unit tests, UI tests, async testing, test architecture.

CharlesWiltgen/Axiom · 38 tokens

designing-tests

Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.

CloudAI-X/claude-workflow-v2 · 48 tokens

test-automation

Execute Vitest and Playwright test suites with result collection and failure analysis.

a5c-ai/babysitter · 0 tokens

testing-blocks

Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.

adobe/skills · 61 tokens

prd-auto-test-loop

A testing workflow driven by a product requirements document (PRD), which describes what a software version should do. It turns acceptance criteria into unit, integration, and end-to-end tests, then records the plan and results.

yunshu0909/yunshu_skillshub · 79 tokens

test-automation-expert

Comprehensive test automation specialist covering unit, integration, and E2E testing strategies. Expert in Jest, Vitest, Playwright, Cypress, pytest, and modern testing frameworks. Guides test pyramid design, coverage optimization, flaky test detection, and CI/CD integration. Activate on 'test strategy', 'unit tests'…

curiositech/some_claude_skills · 133 tokens

test-plan