regression-consistency-checker

Name: regression-consistency-checker
Availability: InStock
Author: ArabelaTso

Compare test execution results between two repository versions to detect regressions.

142|14|Updated Feb 14, 2026

Search Tags:#ci/cd #test automation #version control #software quality #regression testing #code comparison

Ready to run

npx skills add https://github.com/ArabelaTso/Skills-4-SE --skill regression-consistency-checker

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: regression-consistency-checker
Source: https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/regression-consistency-checker
Command: npx skills add https://github.com/ArabelaTso/Skills-4-SE --skill regression-consistency-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pytest, difflib, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that new versions of code do not introduce regressions by comparing test outcomes against a previous version, safeguarding against unintended behavior changes.

Core Features & Use Cases

Regression Detection: Identifies critical, high, medium, and low severity regressions in test passes, outputs, exceptions, and performance.
Behavior Preservation: Verifies that refactoring, bug fixes, or new features do not break existing functionality.
Use Case: After updating a library, use this Skill to run your entire test suite against both the old and new versions to confirm that no existing tests fail and that critical functionality remains intact.

Quick Start

Use the regression-consistency-checker skill to compare test results between the 'old-version' tag and the 'new-version' tag.

Frequently Asked Questions about regression-consistency-checker

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

FAQPage Schema

How do I detect test regressions between two code versions?▼

Run your test suite using pytest against two repository versions to detect regressions by analyzing differences in test passes, output values, exceptions, and performance metrics. This automated comparison identifies unintended behavior changes introduced by refactoring or library updates.

Can I use pytest to verify behavior preservation after refactoring?▼

Yes, you can use pytest to verify behavior preservation after refactoring by running the regression checker. It compares test outcomes against a previous version to ensure bug fixes or new features do not break existing functionality or introduce unintended behavior changes.

What types of regressions are identified during code version comparison?▼

Code version comparison identifies critical, high, medium, and low severity regressions in test passes, outputs, exceptions, and performance metrics. This severity classification helps prioritize which unintended behavior changes require immediate attention before deploying new code versions.

Does the regression checker work with difflib for code comparison?▼

Yes, the regression checker uses difflib alongside pytest to compare test execution results between repository versions. This combination enables detailed analysis of output differences and exception changes, ensuring comprehensive regression detection across your test suite.

What's the best way to automate regression testing for library updates?▼

Automate regression testing for library updates by running your entire test suite against both old and new versions using the regression consistency checker. This confirms no existing tests fail and critical functionality remains intact, safeguarding backward compatibility.

When do I need regression testing after updating a library?▼

You need regression testing after updating a library when you want to confirm that no existing tests fail and critical functionality remains intact. Compare test outcomes between old and new versions to detect severity-ranked regressions in outputs, exceptions, and performance.