regression-check

Analyzes Git diffs and executes relevant unit, integration and E2E tests to detect regressions.

105|8|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/686f6c61/alfred-dev --skill regression-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: regression-check
Source: https://github.com/686f6c61/alfred-dev/tree/main/skills/calidad/regression-check
Command: npx skills add https://github.com/686f6c61/alfred-dev --skill regression-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents new code changes from breaking existing functionality, a common source of user frustration and development rework.

Core Features & Use Cases

  • Impact Analysis: Systematically identifies all parts of the codebase potentially affected by a change.
  • Targeted Testing: Executes relevant tests (unit, integration, e2e) on affected modules.
  • Regression Detection: Differentiates between actual regressions and incorrect test expectations.
  • Use Case: After a developer modifies a core authentication module, this Skill ensures that login, registration, and password reset functionalities (which rely on the authentication module) remain fully operational.

Quick Start

Run the regression-check skill to verify that recent code modifications have not introduced any unintended side effects.

Frequently Asked Questions about regression-check

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

FAQPage Schema
How do I prevent new code changes from breaking existing functionality?

Regression testing verifies that new code modifications do not introduce unintended side effects by analyzing change impact and executing targeted tests on affected modules.

How does regression testing identify affected modules in a codebase?

Impact analysis identifies all affected modules by using Git diff analysis to systematically map the potential impact of recent code changes across the codebase.

Do I need Git and a test runner to perform automated change impact analysis?

Yes, automated change impact analysis requires Git for diff analysis and a test runner to execute unit, integration, and end-to-end tests against the affected modules.

Can regression testing differentiate between actual regressions and incorrect test expectations?

Yes, regression detection differentiates between actual regressions and incorrect test expectations by analyzing the impact of intentional code modifications on existing functionality.

What is the best way to run targeted tests after modifying a core module?

The best way is to use regression testing to identify affected modules via Git diff analysis and execute relevant unit, integration, and e2e tests on those specific areas.

When should I not use regression testing for code review?

Regression testing is not suitable when you lack a Git repository for diff analysis or when no test runner is configured to execute unit, integration, or e2e tests on affected modules.