Forge-Regression-Testing

Selects and executes regression test suites to detect unintended behavior changes after code modifications.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/Nealsch/ForgeOS --skill forge-regression-testing-nealsch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Forge-Regression-Testing
Source: https://github.com/Nealsch/ForgeOS/tree/main/Framework/05-Skills/04-Quality/Forge-Regression-Testing
Command: npx skills add https://github.com/Nealsch/ForgeOS --skill forge-regression-testing-nealsch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Software changes such as fixes, enhancements, and refactoring can silently break previously working functionality. This Skill provides a structured process for selecting regression scope, maintaining regression suites, and verifying that existing behavior survives change before release. ## Core Features & Use Cases - Risk-Based Scope Selection: Identifies which existing behavior must be re-verified based on the change set and dependency analysis. - Living Regression Suite: Curates the suite continuously by adding cases from fixed defects and retiring obsolete tests. - Baseline Comparison: Executes the suite against the build under test and compares results against the regression baseline, reporting any behavioral change with evidence. - Use Case: Before merging a refactoring branch, use this Skill to select the affected regression scope, run the suite, and hand any confirmed regressions to defect management with documented evidence. ## Quick Start Ask the AI to select and execute a regression test scope for the current change set and report any behavioral differences against the existing baseline.

Frequently Asked Questions about Forge-Regression-Testing

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

FAQPage Schema
How do I select regression test scope for a code change?▼

Regression scope is selected based on what changed and what depends on it, using risk and dependency analysis. High-risk and high-traffic behavior is prioritized so the earliest practical feedback signal is produced.

How to maintain a regression test suite over time?▼

Treat the suite as a living asset: add a regression case for every fixed defect and retire obsolete tests continuously. This keeps the suite current, trusted, and maintainable as the product evolves.

When should regression testing not be used?▼

Do not use it for first-pass testing of new features, defining overall test strategy, performance or load testing, debugging root causes, or release readiness assessment. Those activities belong to their own dedicated testing skills.

What is the difference between regression testing and test execution?▼

Regression testing re-verifies existing behavior after change by comparing results against a baseline, while general test execution covers first-pass validation of new functionality. Regression testing guards accumulated quality rather than validating new features.

What happens when a regression is found during testing?▼

Any behavioral change discovered is surfaced explicitly with evidence, never absorbed quietly. Confirmed regressions are handed to defect management, and the baseline is updated only after changes are accepted.