New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Regression Test Plan

by mohitagw15856 in mohitagw15856/pm-claude-skills

Design and prioritize a regression test suite so changes don't break what worked.

MITAuto-check passedTesting & QA

Install Regression Test Plan

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill regression-test-plan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills regression-test-plan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/regression-test-plan .claude/skills/regression-test-plan && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
regression-test-plan
GitHub stars
1.4k
Token cost
~960 tokens
SKILL.md length
466 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

Design and prioritize a regression test suite so changes don't break what worked.

  • Asked to plan regression testing
  • SKILL.md covers Working from a brief, Required Inputs, Output Format and Quality Checks, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Build a regression suite

What it does

Regression Test Plan is an agent skill from mohitagw15856/pm-claude-skills. Design and prioritize a regression test suite so changes don't break what worked. Use when asked to plan regression testing, build a regression suite, decide what to re-test after a change, or trim a bloated regression pack. Produces a risk-based regression plan — what to re-test and why, prioritised tiers (smoke → full), automation candidates, and a run strategy per release — so coverage matches risk and the suite stays fast.

Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering QA and bug reports. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Asked to plan regression testing
  • Build a regression suite
  • Decide what to re-test after a change
  • Trim a bloated regression pack

Example prompts

  • “/regression-test-plan”

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Regression Test Plan loads about 960 tokens when it runs. Until then it costs about 113 tokens; SKILL.md has 466 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~113
When it runs · the whole SKILL.md, loaded when a task matches
~960

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 466 words, ~960 tokens.

Download SKILL.mdSave it as .claude/skills/regression-test-plan/SKILL.md (or your agent's skills folder).
name
regression-test-plan
description
Design and prioritize a regression test suite so changes don't break what worked. Use when asked to plan regression testing, build a regression suite, decide what to re-test after a change, or trim a bloated regression pack. Produces a risk-based regression plan — what to re-test and why, prioritised tiers (smoke → full), automation candidates, and a run strategy per release — so coverage matches risk and the suite stays fast.

Regression Test Plan Skill

Regression testing protects what already works — but re-running everything every time is slow and wasteful, and testing too little ships breakage. The answer is risk-based: re-test what changed, what it touches, and what hurts most if it breaks. This skill builds that prioritised plan and a run strategy, so coverage tracks risk and the suite doesn't balloon.

Working from a brief

Given "we're shipping a checkout change, what should we regression-test?", produce the plan anyway — infer the impacted areas and a sensible prioritisation, labelling assumptions. Tie scope to change-impact and risk. Never hand back a question instead of a plan.

Required Inputs

Ask for these only if they aren't already provided (else infer and label):

  • The change — what's being released/modified, and what it touches (and integrates with).
  • Critical paths — the flows that must never break (revenue, auth, data integrity).
  • Existing coverage — current regression cases/automation, if any, and how long a full run takes.
  • Constraints — time/resources per release, and manual vs. automated capacity.

Output Format

Regression Plan: [release/change]

1. Impact analysis — what changed, the areas directly and indirectly affected, and the high-risk zones (shared components, recent bugs, complex logic).

2. Prioritised scope — what to re-test, in tiers:

TierWhen to runScopeWhy
Smoke / sanityevery buildcritical paths only (login, checkout, save)fast fail
Targetedthis changethe changed area + its direct dependencieschange-impact
Full regressionmajor release / risky changebroad core coveragesafety net

3. What to skip (and the risk) — explicitly de-scope low-risk, unchanged areas, and name the residual risk.

4. Automation candidates — which cases are stable, high-value, and repetitive enough to automate first (and which to keep manual).

5. Run strategy — when each tier runs (per-commit / per-release), order (critical first), and the entry/exit criteria for sign-off.

Show full SKILL.md (173 more words)Show less

Quality Checks

  • Scope is driven by change-impact and risk, not "run everything" or "run the same list every time"
  • Critical paths are always covered (a fast smoke tier)
  • De-scoped areas are explicit, with the residual risk named
  • Automation candidates are prioritised by stability and value
  • A run strategy ties each tier to when it runs and the sign-off criteria
  • The suite stays proportionate to the time/risk — not bloated

Anti-Patterns

  • Do not "re-run everything" by default — it's slow and trains teams to skip it
  • Do not test only the changed file — cover its dependencies and shared components
  • Do not silently drop coverage — when you de-scope, state the risk
  • Do not automate flaky or rarely-run cases first — start with stable, high-value ones
  • Do not let the suite grow unbounded — prune and tier it as the product changes

Based On

Risk-based regression practice — change-impact analysis, tiered smoke/targeted/full suites, automation prioritisation, and release-fit run strategy.

Example Trigger Phrases

  • "Plan regression testing."
  • "Build a regression suite."
  • "Decide what to re-test after a change."
  • "Trim a bloated regression pack."

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/regression-test-plan of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Regression Test Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Regression Test Plan compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Regression Test Plan this skillmohitagw15856/pm-claude-skills1.4k—~960Automated safety check: PassMIT
Reproduce Chat Statesdifferent-ai/openwork24k—~673Automated safety check: PassCustom licence
Dynamo Jira TicketDynamoDS/Dynamo2k—~1.1kAutomated safety check: PassApache-2.0
Moav E2EMotherofallVPNs/MoaV448—~1.9kAutomated safety check: NotesMIT
Creating A Coral TaskHuman-Agent-Society/CORAL1.1k—~2.2kAutomated safety check: PassApache-2.0
Launch Rlmarin-community/marin3.9k—~894Automated safety check: PassApache-2.0

Similar skills

  • Reproduce Chat States

    different-ai/openwork

    Fires known chat states in the running OpenWork desktop app, such as provider errors, retries and tool steps, so you can check how each renders.

    24k GitHub stars~673 tokensUpdated today
    Testing & QAAuto-check passed

  • Dynamo Jira Ticket

    DynamoDS/Dynamo

    Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.

    2k GitHub stars~1.1k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Moav E2E

    MotherofallVPNs/MoaV

    Run and debug MoaV's end-to-end tests — real protocol connectivity (client-test.sh) and the moav CLI smoke test — against a LIVE server, via the self-hosted e2e workflow or a local test VPS.

    448 GitHub stars~1.9k tokensUpdated 2 days ago
    Testing & QAAuto-check: notes

  • Creating A Coral Task

    Human-Agent-Society/CORAL

    Author a new CORAL task — the three pieces that must line up (task.yaml, seed/, a packaged grader/), the coral init → coral validate → smoke-test loop, and how to pick a grader pattern (stdout…

    1.1k GitHub stars~2.2k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

  • Launch Rl

    marin-community/marin

    Define, validate, submit, or restart a Marin SkyRL experiment through its artifact main.

    3.9k GitHub stars~894 tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Actionbook Web Test

    actionbook/actionbook

    Run browser-based web tests against websites using Actionbook CLI.

    1.6k GitHub stars~9.7k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo

  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Regression Test Plan

What does Regression Test Plan do?

Design and prioritize a regression test suite so changes don't break what worked. Regression Test Plan is an agent skill from mohitagw15856/pm-claude-skills. Design and prioritize a regression test suite so changes don't break what worked.

When should I use Regression Test Plan?

Regression Test Plan fits situations like: asked to plan regression testing; build a regression suite; decide what to re-test after a change; trim a bloated regression pack.

How do I install Regression Test Plan in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill regression-test-plan -a claude-code`. Or copy the skill folder (skills/regression-test-plan in mohitagw15856/pm-claude-skills) into .claude/skills/regression-test-plan in your project. Claude Code loads it when a task matches its description.

How do I install Regression Test Plan in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill regression-test-plan -a codex`. Or copy the skill folder (skills/regression-test-plan in mohitagw15856/pm-claude-skills) into .agents/skills/regression-test-plan in your project. Codex loads it when a task matches its description.

Can I use Regression Test Plan in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill regression-test-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/regression-test-plan, .gemini/skills/regression-test-plan, .github/skills/regression-test-plan and .opencode/skills/regression-test-plan in your project.

What does Regression Test Plan need to run?

SKILL.md names no scripts, command-line tools or credentials: Regression Test Plan is instructions for the agent only.

Does Regression Test Plan access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Regression Test Plan safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Regression Test Plan use?

Regression Test Plan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Regression Test Plan use?

About 960 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Regression Test Plan?

Skills that share tags, products or a category with Regression Test Plan: Reproduce Chat States (different-ai/openwork, 24k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars), Moav E2E (MotherofallVPNs/MoaV, 448 stars) and Creating A Coral Task (Human-Agent-Society/CORAL, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Regression Test Plan?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,433 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 8, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.