skills.rest
Negentropy-Laby
Negentropy-LabyOFFICIAL
Explore all skills by this author →
GitHub

regression-suite

Audit test inventories and generate regression suite manifests for release gating.

3|Updated Jun 3, 2026
Search Tags:#automation#testing#qa#regression#coverage#bug-fix#regression-suite
One-click install
npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill regression-suite-negentropy-laby
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: regression-suite
Source: https://github.com/Negentropy-Laby/Constitution-Driven-Development/tree/main/.agents/skills/regression-suite
Command: npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill regression-suite-negentropy-laby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that every bug fix is backed by a test that would have caught the original bug — and that the regression suite stays current as the game evolves. It also detects when new features have been added without corresponding regression coverage.

Core Features & Use Cases

  • Maintains a curated list of tests that cover critical paths and known failure points.
  • Detects gaps between bugs fixed and regression tests; updates the central manifest and provides drift indicators to keep QA aligned with development.
  • Supports audit, update, and report workflows to streamline sprint planning and release gates.

Quick Start

Run /regression-suite update after a sprint to refresh the registry and ensure new bugs have regression coverage.

Frequently Asked Questions about regression-suite

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

FAQPage Schema
How do I maintain a regression suite that covers bug fixes in a delivery pipeline?▼

Maintain a regression suite by auditing the test inventory and generating a manifest that maps coverage to critical paths, ensuring every bug fix is backed by a test that catches the original failure.

How does regression test coverage mapping detect drift in software delivery pipelines?▼

Regression coverage mapping detects drift by loading critical paths from the CDD and comparing them against the test inventory, highlighting gaps where new features or bug fixes lack corresponding regression tests.

Can I apply regression suite updates across different platforms like APIs, CLIs, and data pipelines?▼

Yes, you can apply regression suite updates across APIs, CLIs, web apps, SDKs, games, and data pipelines to map coverage to critical paths and detect drift consistently.

What is the best way to update regression coverage after a sprint?▼

The best way to update regression coverage after a sprint is to run an update command that refreshes the test registry, audits new bug fixes, and updates the central manifest for release gating.

Why does my QA process miss regressions for newly added features?▼

Your QA process misses regressions when the test inventory is not audited against critical paths, causing drift indicators to fail and leaving new features without corresponding regression coverage in the manifest.

Do I need a manifest to gate releases with a regression suite?▼

Yes, you need a manifest to gate releases because it guides QA by mapping the curated regression tests to critical paths and known failure points, enforcing updates as the software evolves.

Related Skills

Explore More Software Engineering Skills→
solace-illsolace-ill

regression-suite

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

Community
Intermediate
LordKuperLordKuper

regression-suite

Map tests to GDD critical paths and flag coverage drift.

Community
Intermediate
J03Fr0stJ03Fr0st

ci-cd-and-automation

Automate CI/CD pipeline setup with GitHub Actions and quality gates.

Community
Advanced
levnikolaevichlevnikolaevich
534

ln-632-test-e2e-priority-auditor

Audit E2E test coverage for critical paths and core journeys.

Community
Advanced