skills.rest
cenconq25
cenconq25COMMUNITY
Explore all skills by this author →
GitHub

regression-suite

Map test coverage to PRD critical paths and flag drift.

39|6|Updated May 3, 2026
Search Tags:#testing#qa#regression#coverage#test-automation#regression-suite
One-click install
npx skills add https://github.com/cenconq25/claude-code-app-studio --skill regression-suite-cenconq25
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: regression-suite
Source: https://github.com/cenconq25/claude-code-app-studio/tree/main/.claude/skills/regression-suite
Command: npx skills add https://github.com/cenconq25/claude-code-app-studio --skill regression-suite-cenconq25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Regression suite maintenance, mapping tests to PRD critical paths, flagging coverage drift, and keeping tests/regression-suite.md up to date.

Core Features & Use Cases

  • Trace PRD-critical paths to regression tests and ensure coverage
  • Identify gaps between PRD requirements, known bugs, and existing tests
  • Plan regression work after bug fixes or before releases with a living registry

Quick Start

Create or update the regression registry and run the suite audit with /regression-suite --audit to map coverage to PRD paths.

Frequently Asked Questions about regression-suite

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

FAQPage Schema
How do I map regression test coverage to PRD critical paths?▼

Regression coverage mapping connects your PRD critical paths to existing regression tests by reading PRDs, bug histories, and regression files. This process surfaces coverage gaps before releases and keeps your tests/regression-suite.md registry up to date.

What is regression coverage drift and how do I flag it after feature changes?▼

Regression coverage drift occurs when feature changes break the alignment between PRD requirements and existing tests. You can flag this drift by running a regression suite audit that reads updated PRDs and bug histories to automatically surface missing test coverage.

How do I identify test coverage gaps from PRD requirements and known bugs?▼

Identifying test coverage gaps requires tracing PRD critical paths against existing regression tests and bug histories. Running an audit compares these sources to highlight missing test scenarios and outputs the results into a living regression registry.

Can I plan regression testing work before a software release using a test registry?▼

Yes, you can plan regression work before releases by maintaining a living test registry. Auditing this registry against PRD critical paths and recent bug fixes identifies the exact test coverage gaps that need attention prior to deployment.

Does this regression suite audit require any specific test automation frameworks?▼

No specific test automation frameworks are required as dependencies. The audit process works by reading your PRDs, bug histories, and regression files directly to map test coverage and maintain a markdown-based regression registry.

Related Skills

Explore More Software Engineering Skills→
Euraika-LabsEuraika-Labs
14

regression-suite

Map test coverage to GDD critical paths and audit regression tests for bug fixes.

Official
Advanced
dnkrowdnkrow
1

regression-suite

Map regression coverage to GDD acceptance criteria and closed-bug fixes.

Community
Advanced
nguyennd93nguyennd93

regression-suite

Scan bug fixes and audit regression test coverage against GDD critical paths.

Community
Advanced
jmaglyjmagly
175

traceability-check

Maps requirements to code and tests, computes coverage gaps and generates a traceability report.

Community
Intermediate