regression-testing
Orchestrates regression test pipelines and provides actionable release-readiness insights.
Install
mkdir -p .claude/skills/regression-testing && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18122" && unzip -o skill.zip -d .claude/skills/regression-testing && rm skill.zipInstalls to .claude/skills/regression-testing
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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).Key capabilities
- →Trigger CI suite runs through GitHub Actions
- →Monitor CI workflow runs to completion
- →Classify test failures into categories like REGRESSION or FLAKY
- →Compute pass-rate and trend metrics for test results
- →Generate executive quality reports for stakeholders
- →Create regression issues in Jira based on analysis
How it works
The skill orchestrates the release-readiness pipeline by triggering a CI suite, monitoring its completion, classifying failures, and scoring against release criteria. It then emits a verdict and a stakeholder report.
Inputs & outputs
When to use regression-testing
- →Trigger smoke test suites
- →Analyze nightly test failures
- →Generate quality reports for stakeholders
- →Classify flaky vs. regression tests
About regression-testing
Manages the lifecycle of regression testing, including triggering CI/CD workflows, analyzing failure patterns, and generating executive reports for go/no-go decisions.
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
When not to use it
- →Writing new regression tests
- →Performing manual fix verification
Limitations
- →Cannot be used for writing new regression tests
- →Cannot be used for manual fix verification
- →Does not allow skipping analysis before generating a report
How it compares
This skill automates the entire release-readiness pipeline from execution to reporting, unlike manual processes that require separate steps for triggering, monitoring, analysis, and reporting.
Compared to similar skills
regression-testing side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| regression-testing (this skill) | 0 | 2mo | Review | Advanced |
| cicd-diagnostics | 1 | 5mo | Review | Advanced |
| posthog-ci-integration | 1 | 1mo | Caution | Intermediate |
| verification-quality-assurance | 1 | 4mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
cicd-diagnostics
dotCMS
Diagnoses DotCMS GitHub Actions failures (PR builds, merge queue, nightly, trunk). Analyzes failed tests, root causes, compares runs. Use for "fails in GitHub", "merge queue failure", "PR build failed", "nightly build issue".
posthog-ci-integration
jeremylongshore
Configure PostHog CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating PostHog tests into your build process. Trigger with phrases like "posthog CI", "posthog GitHub Actions", "posthog automated tests", "CI posthog".
verification-quality-assurance
ruvnet
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
circleci-why-flaky
mui
Classify recent CircleCI workflow failures into buckets so you can see what's flake vs what's a real bug. Use when CI on a branch is failing repeatedly and you want to know whether retries will fix it. Infers project + branch from the current git repo; defaults to last 7 days.
ci
PioneersHub
Run the local CI pipeline (ruff, bandit, pytest, sonar-scanner) and refresh SonarQube.
qa-tester
svilupp
Browser automation QA testing skill. Systematically tests web applications for functionality, security, and usability issues. Reports findings by severity (CRITICAL/HIGH/MEDIUM/LOW) with immediate alerts for critical failures.