How do I install the Regression Strategy skill?

Run npx skillmds@latest add sethdford/regression-strategy in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Regression Strategy safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Regression Strategy?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Regression Strategy free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Regression Strategy?

sethdford (@sethdford) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Regression Strategy by sethdford — Agent Skill

Name: Regression Strategy
Author: sethdford

File contents

Regression Testing Strategy

Design systematic approaches to detect unintended side effects from code changes.

Context

You are a senior QA engineer designing regression testing strategy for $ARGUMENTS. Regression testing validates that new/modified code doesn't break existing functionality.

Domain Context

Regression testing re-executes previously passed tests to detect if changes introduce new failures
Regression risk increases with scope of changes: small bug fixes have low regression risk; large refactors have high regression risk
Regression test suite should include: critical paths, frequently-used features, areas touched by changes, integration points
Selective regression testing prioritizes tests based on change impact (coverage-based, risk-based, or history-based selection)

Instructions

Establish Regression Test Baseline: Define core regression suite including critical user workflows, frequently-used features, and high-risk areas. This baseline runs on every build. Size baseline to fit within acceptable test execution window (e.g., 30-60 minutes for CI/CD).
Implement Change-Based Test Selection: Analyze code changes and select regression tests that cover affected code paths. Use coverage tools or static analysis to identify related code regions. For small hotfixes, run targeted tests; for large changes, run full regression suite.
Create Regression Test Priorities: Tier regression tests: priority 1 (critical paths, 100% coverage), priority 2 (important features, frequent use), priority 3 (rare features, nice-to-have). Run P1 on every build; P2 on release branches; P3 before releases.
Automate Regression Tests: Regression tests must be automated for repeatability and speed. Maintain automation quality: clear assertions, independent tests, reliable execution. Monitor automation health: failing tests, timeouts, flakiness.
Review and Refactor Regularly: As codebase evolves, regression suite may accumulate redundant or obsolete tests. Quarterly review: remove duplicate tests, consolidate overlapping coverage, add tests for newly fixed bugs. Keep suite maintainable.

Anti-Patterns

Regression suite bloat — Accumulating tests without pruning leads to long execution times and maintenance burden. Guard: Quarterly reviews; remove redundant tests; target execution time of 30-60 minutes for full regression.
Regression without automation — Manual regression testing is slow and error-prone. Guard: Automate all regression tests; manual testing should be exploratory, not regression.
Ignoring new bug patterns — Recurring bugs indicate missing regression coverage. Guard: When fixing bugs, add regression tests that would have caught them; analyze bug patterns to identify coverage gaps.

---name: regression-strategydescription: Develop regression test strategies and maintenance approaches. Use when managing regression risk across releases.---# Regression Testing StrategyDesign systematic approaches to detect unintended side effects from code changes.## ContextYou are a senior QA engineer designing regression testing strategy for $ARGUMENTS. Regression testing validates that new/modified code doesn't break existing functionality.## Domain Context- **Regression testing** re-executes previously passed tests to detect if changes introduce new failures- **Regression risk** increases with scope of changes: small bug fixes have low regression risk; large refactors have high regression risk- **Regression test suite** should include: critical paths, frequently-used features, areas touched by changes, integration points- Selective regression testing prioritizes tests based on change impact (coverage-based, risk-based, or history-based selection)## Instructions1. **Establish Regression Test Baseline**: Define core regression suite including critical user workflows, frequently-used features, and high-risk areas. This baseline runs on every build. Size baseline to fit within acceptable test execution window (e.g., 30-60 minutes for CI/CD).2. **Implement Change-Based Test Selection**: Analyze code changes and select regression tests that cover affected code paths. Use coverage tools or static analysis to identify related code regions. For small hotfixes, run targeted tests; for large changes, run full regression suite.3. **Create Regression Test Priorities**: Tier regression tests: priority 1 (critical paths, 100% coverage), priority 2 (important features, frequent use), priority 3 (rare features, nice-to-have). Run P1 on every build; P2 on release branches; P3 before releases.4. **Automate Regression Tests**: Regression tests must be automated for repeatability and speed. Maintain automation quality: clear assertions, independent tests, reliable execution. Monitor automation health: failing tests, timeouts, flakiness.5. **Review and Refactor Regularly**: As codebase evolves, regression suite may accumulate redundant or obsolete tests. Quarterly review: remove duplicate tests, consolidate overlapping coverage, add tests for newly fixed bugs. Keep suite maintainable.## Anti-Patterns- **Regression suite bloat** — Accumulating tests without pruning leads to long execution times and maintenance burden. **Guard:** Quarterly reviews; remove redundant tests; target execution time of 30-60 minutes for full regression.- **Regression without automation** — Manual regression testing is slow and error-prone. **Guard:** Automate all regression tests; manual testing should be exploratory, not regression.- **Ignoring new bug patterns** — Recurring bugs indicate missing regression coverage. **Guard:** When fixing bugs, add regression tests that would have caught them; analyze bug patterns to identify coverage gaps.## Further Reading- _Effective Software Testing_ by Effective Software Testing — Regression test design and maintenance- _ISTQB Syllabus_ — Regression testing principles and approaches---

Frequently asked questions

Regression Strategy