regression-suite
FeaturedMap test coverage to GDD critical paths, identify fixed bugs without regression tests, flag coverage drift from new features, and maintain tests/regression-suite.md. Run after implementing a bug fix or before a release gate.
Install
Quality Score: 97/100
Skill Content
Details
- Author
- Donchitos
- Repository
- Donchitos/Claude-Code-Game-Studios
- Created
- 9 months ago
- Last Updated
- 1 weeks ago
- Language
- Shell
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
regression-suite
Map test coverage to GDD critical paths, identify fixed bugs without regression tests, flag coverage drift from new features, and maintain tests/regression-suite.md. Run after implementing a bug fix or before a release gate.
regression-manager
Manages the regression suite over time — verifying fixes, removing expected-failure markers when defects are resolved, merging new tests into the regression set with the right tags, retiring obsolete tests, and triaging flakiness before it erodes trust. Use this skill when a defect has been fixed and needs re-verification, when new tests should join the regression suite, when the suite is getting slow or unreliable, or when the user asks what to run before a release. Also use it to audit an inherited suite for dead and duplicated tests.
regression-testing
Execute regression test suites via CI/CD, analyze results, classify failures, and produce GO/NO-GO release decisions. Use when running regression, smoke, or sanity suites through GitHub Actions, monitoring workflow runs, downloading Allure or Playwright artifacts, classifying failures (REGRESSION vs FLAKY vs KNOWN vs ENVIRONMENT vs NEW TEST), computing pass-rate and trend metrics, deciding release readiness, generating executive quality reports, or creating regression issues. Triggers on: run regression, trigger test workflow, analyze test results, quality report, GO/NO-GO decision, release readiness, flaky tests, Allure report, smoke suite, pass rate, nightly test failure, stage 6. Do NOT use for writing new regression tests (that belongs to test-automation) or for manual fix verification (that belongs to sprint-testing).