regression-suite-curator

Curate regression and smoke test membership using CI history and coverage evidence.

2|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill regression-suite-curator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: regression-suite-curator
Source: https://github.com/nguyenpv1980-wq/Project-Aegis/tree/main/.claude/skills/regression-suite-curator
Command: npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill regression-suite-curator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams decide which tests belong in regression and smoke suites, which should be promoted, demoted, quarantined, or retired, and how to keep suite runtime within budget without losing meaningful protection.

Core Features & Use Cases

  • Evidence-based curation: Builds a decision list using CI history, runtime, failure patterns, duplicate coverage, and ownership signals.
  • Promotion and retirement rules: Ensures fixed bugs and postmortem gaps map to regression coverage, while dead, duplicate, or unreachable tests are retired with written rationale.
  • Quarantine enforcement: Requires every quarantined test to have an owner, ticket, and expiry, and forces a decision when quarantine entries expire.
  • Protected security regressions: Treats security regression tests as a protected class that can only be retired through the human-approval path.
  • Use case: A bloated suite is slowing releases, so this Skill trims low-value coverage, preserves critical journeys, and documents every change to test membership.

Quick Start

Use the regression-suite-curator skill to audit this test suite, identify promotion and retirement candidates, enforce quarantine rules, and produce a curation decision list with evidence.

Frequently Asked Questions about regression-suite-curator

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

FAQPage Schema
How do I reduce regression test suite runtime without losing critical coverage?

Regression suite curation trims low-value tests using CI history, runtime data, and coverage context to promote, demote, quarantine, or retire tests, keeping suites lean while enforcing runtime budgets across CI tiers.

What is the best way to manage quarantined tests in a CI pipeline?

Quarantine enforcement requires every quarantined regression test to have an assigned owner, tracking ticket, and expiry date, forcing a decision to promote or retire the test when its quarantine period expires.

How do I promote bug-fix regression tests into my main suite?

Evidence-based curation maps fixed bugs and postmortem gaps to regression coverage by promoting corresponding tests, ensuring bug fixes have documented regression protection before entering the main suite.

Does this regression curation approach protect security regression tests from being retired?

Security regression tests are treated as a protected class that can only be retired through a human-approval path, preventing automated curation from removing critical security coverage from the regression suite.

What inputs do I need before curating a bloated regression suite?

Regression suite curation requires CI history, coverage context, ownership signals, and runtime data to build an evidence-based decision list that identifies which tests to promote, demote, quarantine, or retire.

When should I retire duplicate or dead tests from my smoke suite?

Dead, duplicate, or unreachable tests should be retired when CI history and coverage context show no meaningful protection, with written rationale documenting every change to smoke and regression suite membership.