regression-check

Run unit, integration, and end-to-end tests to detect regressions.

15|5|Updated May 17, 2026
One-click install
npx skills add https://github.com/cropsgg/skills --skill regression-check-cropsgg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: regression-check
Source: https://github.com/cropsgg/skills/tree/main/skills/engineering/regression-check
Command: npx skills add https://github.com/cropsgg/skills --skill regression-check-cropsgg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects and prevents regressions by running and interpreting tests before merges or releases.

Core Features & Use Cases

  • Run unit, integration, and end-to-end tests and summarize failures.
  • Provide actionable guidance to fix regressions and update test coverage.
  • Use during pre-merge checks, post-refactor validations, and dependency upgrades to guard against unintended changes.

Quick Start

Run the regression-check workflow locally to validate your changes before pushing a merge request.

Frequently Asked Questions about regression-check

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

FAQPage Schema
How do I run regression tests before a merge to catch unintended changes?

Run regression tests during pre-merge CI to detect unintended changes in software builds. The workflow executes unit, integration, and end-to-end tests, summarizing failures to prevent regressions before merges or releases.

What is the best way to validate software behavior after a dependency upgrade?

Validating software behavior after dependency upgrades requires running regression checks across test suites. This identifies unintended changes introduced by new dependencies and provides actionable guidance to fix detected regressions and improve test coverage.

Can I use this for post-refactor validations in my CI pipeline?

Yes, you can use this for post-refactor validations in your CI pipeline. It guards against unintended changes by running and interpreting tests, ensuring refactoring efforts do not introduce regressions into the software builds.

How do I get actionable guidance to fix failing test coverage?

To get actionable guidance to fix failing test coverage, the workflow interprets standardized failure reports from deterministic test results. It then provides specific recommendations to resolve regressions and update your test coverage accordingly.

Do I need deterministic test results to interpret test failures?

Yes, you need deterministic test results to accurately interpret test failures. The regression check requires access to deterministic test outcomes and standardized failure reports to reliably detect and prevent unintended software changes.

What are the limitations of automated regression testing for end-to-end tests?

Automated regression testing for end-to-end tests relies on deterministic test results and standardized failure reports. If tests are flaky or lack standardized reporting, the regression check may struggle to accurately identify unintended changes in software behavior.