skills.rest
CarlosQ96
CarlosQ96COMMUNITY
Explore all skills by this author →
GitHub

regression-suite

Map test coverage to GDD critical paths and flag gaps.

Updated Apr 9, 2026
Search Tags:#test-coverage#gdd#regression-testing#bug-fixes#qa-audit#test-registry
One-click install
npx skills add https://github.com/CarlosQ96/robot-crawler --skill regression-suite
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: regression-suite
Source: https://github.com/CarlosQ96/robot-crawler/tree/main/.agents/skills/regression-suite
Command: npx skills add https://github.com/CarlosQ96/robot-crawler --skill regression-suite

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maps test coverage to GDD critical paths, identifies gaps where regression tests are missing, flags coverage drift from new features, and maintains tests/regression-suite.md. Run after implementing a bug fix or before a release gate.

Core Features & Use Cases

  • Curates a regression test registry that maps existing tests to GDD acceptance criteria and edge cases.
  • Audits, updates, and reports on coverage drift, new features, and fixed bugs to ensure release readiness.
  • Generates and maintains tests/regression-suite.md as a single source of truth for regression gating.

Quick Start

Run a regression-suite update after implementing a bug fix to refresh tests and coverage.

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 GDD acceptance criteria after a bug fix?▼

Test coverage is mapped to GDD acceptance criteria by scanning unit and integration tests, consulting design/gdd files, and flagging missing regression tests for fixed bugs. The audit results update tests/regression-suite.md as a single source of truth.

What is the best way to audit regression test coverage before a release gate?▼

Auditing regression test coverage before a release gate involves scanning tests/unit and tests/integration directories, comparing them against GDD critical paths, and generating a coverage drift report to identify untested edge cases.

How do I maintain a regression test registry that flags coverage drift from new features?▼

A regression test registry is maintained by updating tests/regression-suite.md, mapping existing tests to GDD critical paths, and actively flagging coverage drift introduced by new features to ensure release readiness.

Does this regression testing approach work without external test runner dependencies?▼

Yes, the regression testing approach works without external dependencies by directly reading tests/unit and tests/integration directories and consulting design/gdd files to determine coverage status based on acceptance criteria.

When should I generate a regression suite report for QA audits?▼

A regression suite report for QA audits should be generated immediately after implementing a bug fix or before a release gate, ensuring that coverage gaps and drift are documented in tests/regression-suite.md.

Related Skills

Explore More Software Engineering Skills→
dnkrowdnkrow
1

regression-suite

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

Community
Advanced
brand6brand6

regression-suite

Audit tests against GDD key paths and update the regression registry.

Community
Advanced
packetalienpacketalien

regression-suite

Scan test inventories and flag gaps against GDD critical paths.

Community
Advanced
scomofoscomofo

regression-suite

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

Community
Advanced