regression-verify

Run a revert-and-confirm protocol to verify regression tests catch defects.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/ToanPV90/dotfiles --skill regression-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: regression-verify
Source: https://github.com/ToanPV90/dotfiles/tree/main/claude/.claude/skills/regression-verify
Command: npx skills add https://github.com/ToanPV90/dotfiles --skill regression-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents false confidence after a bug fix by verifying that the fix truly resolves the defect and that the test actually fails on the broken state.

Core Features & Use Cases

  • Regression Cycle (5 steps): Runs the required run–revert–retest–restore–retest protocol so you can distinguish a real fix from a misleading test.
  • Claim-to-Evidence Mapping: Ensures every completion claim is backed by specific terminal output or concrete observed results, not intuition or code review.
  • Anti-Rationalization Guardrails: Blocks common reasoning traps (e.g., “tests passed therefore it’s fixed”) by enforcing the revert-and-fail step as evidence of test validity.
  • Use Case: You fixed a failing test or changed core logic; apply this skill to confirm the defect path is genuinely covered and remains fixed after restoration.

Quick Start

Ask the AI to run the Regression Cycle for the specific test you updated and to produce a claim-to-evidence mapping using the pasted terminal output.

Frequently Asked Questions about regression-verify

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

FAQPage Schema
How do I verify a bug fix actually catches the defect without false confidence?

Verify a bug fix by running a revert-and-confirm regression cycle. This protocol requires reverting the code to the broken state, demonstrating the test fails on the defect, then restoring the fix to confirm it passes.

What is the regression cycle protocol for test validation?

The regression cycle for test validation is a 5-step protocol: run, revert, retest, restore, and retest. This process distinguishes a genuine code fix from a misleading test by proving the test catches the specific defect.

How do I map completion claims to concrete evidence from CI output?

Map completion claims to concrete CI output evidence by enforcing claim-to-evidence mapping. This requires backing every completion assertion with specific terminal logs or observable results, preventing rationalization traps like assuming tests passing means the defect is fixed.

When do I need to use a revert-and-confirm protocol for bug fix verification?

You need a revert-and-confirm protocol for bug fix verification when validating a code change or confirming a test catches the defect. It proves the test genuinely covers the defect path and the fix resolves it.

Why does my test pass even after I revert my bug fix?

If your test passes after reverting a bug fix, the test is misleading and does not catch the defect. The revert-and-fail step in regression testing enforces test validity by requiring the test to fail on the broken state.

Can I use terminal logs to prove my test-driven debugging worked?

Yes, you can use terminal logs to prove test-driven debugging worked by applying claim-to-evidence mapping. This anti-rationalization guardrail ensures every completion claim is backed by specific observable outputs from your regression cycle.