regression-tester

Run regression checks comparing pre-change and post-change behavior with evidence.

11|1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/ylxmf2005/AgentCorp --skill regression-tester
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: regression-tester
Source: https://github.com/ylxmf2005/AgentCorp/tree/main/agentcorp/regression-tester
Command: npx skills add https://github.com/ylxmf2005/AgentCorp --skill regression-tester

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Act as the AgentCorp Regression Tester: prove that behavior which used to work still works after a change. Use when the verify phase needs to guard against behavioral regressions, when a bug fix needs proof against the input that originally failed, or when someone asks whether a change broke anything around it.

Core Features & Use Cases

  • Run regression suites on both pre-change and post-change states to verify preserved behavior.
  • Capture before/after observations, evidence, and environment details to support verdicts.
  • Provide structured results with status, blockers, and residual risk for incomplete checks, ensuring traceability.

Quick Start

Run regression checks that compare pre-change and post-change behavior and capture evidence.

Frequently Asked Questions about regression-tester

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

FAQPage Schema
How do I verify a bug fix doesn't break existing behavior?

Run regression checks comparing pre-change and post-change states to verify behavior preservation. Capture explicit before and after observations, environment details, and residual-risk notes to ensure outcomes remain consistent and provide traceable evidence.

What is regression testing for change management?

Regression testing for change management is the process of proving modifications preserve expected behavior. It runs checks across bug fixes and feature changes, comparing before and after states to capture traceable evidence that outcomes remain consistent.

How do I capture traceable evidence before and after a code change?

Capture traceable evidence by running regression checks on both pre-change and post-change states, requiring explicit before and after observations and environment details. This structured approach ensures verdicts and residual-risk notes are fully traceable.

Can I use regression checks to assess residual risk when behavior differs?

Yes, regression checks assess residual risk when verdicts differ by requiring explicit residual-risk notes. They provide structured results with status and blockers for incomplete checks, ensuring any behavioral differences are documented and traceable.

What do I need to run pre-change and post-change regression checks?

You need explicit before and after observations and environment details to run regression checks. The process applies across bug fixes and feature changes to verify preserved behavior, capturing structured results with status and blockers for incomplete checks.