How do I add a specific test to the regression suite?

You can add a test by asking Claude to 'track regression --mark' followed by the test name, or simply use the 'reg' shortcut.

What is the fastest way to run all regression tests?

You can use the shortcut command 'reg' or ask Claude to 'run regression tests' to trigger the full suite execution.

Can this skill identify unstable or flaky tests?

Yes, the skill analyzes test results and execution history to highlight flaky tests that produce inconsistent results.

Does this work with existing CI/CD tools?

The skill is designed to integrate with your existing workflow, allowing you to bridge the gap between manual coding and automated pipeline execution.

Regression Test Tracker

Name: Regression Test Tracker
Author: intent-solutions-io

byintent-solutions-io

Security & Testing

Automates the identification, execution, and analysis of regression tests to prevent breaking changes and ensure code stability.

About

The Regression Test Tracker skill empowers Claude to manage and execute your regression testing suite seamlessly within your development workflow. By allowing users to mark specific tests, automate execution, and analyze results for failures or flaky behavior, this skill ensures that new feature additions or refactors do not compromise existing functionality. It provides deep insights into test history and impact analysis, making it an essential tool for maintaining high software quality and developer confidence during the deployment cycle.

Key Features

Mark specific tests for the regression suite using simple natural language commands
Impact analysis to determine how code changes affect existing functionality
Automated execution of designated regression test suites
Historical tracking of test results to monitor stability over time
0 GitHub stars
Comprehensive failure analysis and identification of flaky tests

Use Cases

Running a full regression suite before merging code or deploying to production
Marking critical bug-fix tests to ensure issues never resurface in future versions
Analyzing the impact of major refactors on existing application behavior

About

Key Features

Mark specific tests for the regression suite using simple natural language commands
Impact analysis to determine how code changes affect existing functionality
Automated execution of designated regression test suites
Historical tracking of test results to monitor stability over time
0 GitHub stars
Comprehensive failure analysis and identification of flaky tests

Use Cases

Running a full regression suite before merging code or deploying to production
Marking critical bug-fix tests to ensure issues never resurface in future versions
Analyzing the impact of major refactors on existing application behavior