skills.rest
wsman
wsmanCOMMUNITY
Explore all skills by this author →
GitHub

regression-suite

Maps test coverage to critical paths and fixed bugs before release.

18|5|Updated Nov 25, 2025
Search Tags:#qa#test coverage#regression#cdd#bug fixes#release gate
One-click install
npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill regression-suite-wsman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: regression-suite
Source: https://github.com/wsman/MY-DOGE-MICRO/tree/main/.agents/skills/regression-suite
Command: npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill regression-suite-wsman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents regressions from slipping through by tying bug fixes and critical product paths to an explicit test coverage manifest. It helps teams spot missing regression tests, stale coverage, and new features that have outpaced the test suite before a release gate.

Core Features & Use Cases

  • Coverage Audit: Compare existing tests against critical acceptance criteria, formulas, edge cases, and known bug fixes.
  • Regression Gap Detection: Identify bugs that were fixed but never backed by a test, and flag missing coverage for newly completed work.
  • Suite Maintenance: Maintain a curated regression manifest that teams can review before shipping or during sprint closeout.
  • Use Case: After a bug fix lands, use this Skill to verify that a test already protects the failure mode or to recommend the exact missing regression test.

Quick Start

Ask the skill to audit or update regression coverage for the current repository and prepare the changes for tests/regression-suite.md only after you approve them.

Frequently Asked Questions about regression-suite

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map test coverage to critical paths and fixed bugs before a release gate?▼

To map test coverage to critical paths and fixed bugs before a release gate, scan existing tests, CDD acceptance criteria, closed bugs, and drift indicators to identify missing regression tests and update tests/regression-suite.md.

What is the best way to detect missing regression tests after a bug fix lands?▼

Detecting missing regression tests after a bug fix involves auditing closed bugs against current test coverage to verify if a test protects the failure mode, recommending exact missing tests to add to the regression suite.

How do I perform a coverage audit during sprint closeout?▼

Performing a coverage audit during sprint closeout requires comparing existing tests against critical acceptance criteria, formulas, and edge cases to flag stale coverage or newly completed work that outpaced the test suite.

Does this regression suite maintenance approach work for both product and game projects?▼

Yes, regression suite maintenance applies across product or game projects, scanning CDD acceptance criteria and drift indicators to maintain a curated regression manifest for teams to review before shipping.

Why are regressions slipping through despite having existing test coverage?▼

Regressions slip through when new features outpace the test suite or bug fixes lack backing tests, making it necessary to tie critical product paths to an explicit test coverage manifest to spot missing or stale regression tests.

Related Skills

Explore More Software Engineering Skills→
WindXRanWindXRan

regression-suite

Audit regression test suites for GDD critical path coverage gaps.

Community
Advanced
scomofoscomofo

regression-suite

Audit regression test coverage against GDD critical paths and closed bug fixes.

Community
Advanced
solace-illsolace-ill

regression-suite

Parse test inventory and design documents to generate a regression test manifest.

Community
Intermediate
nuoyanruoshuinuoyanruoshui
47

regression-suite

Map automated tests to game design critical paths and fixed bugs.

Community
Advanced