regression-test-development

Create focused regression tests with red-green validation evidence for defects and behavior requirements.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill regression-test-development-quydu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: regression-test-development
Source: https://github.com/QuyDu/Skills-Orchestrator/tree/main/.github/skills/regression-test-development
Command: npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill regression-test-development-quydu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a bug is fixed or a new behavior is requested, teams often lack durable automated tests that would catch the same defect if it returned. This Skill converts a confirmed defect or behavior requirement into focused, maintainable regression coverage with documented execution evidence. ## Core Features & Use Cases - Red-Green Test Development: Writes the smallest test that fails for the missing behavior, applies the minimal production fix, and captures both failing and passing evidence. - Bounded Write Scope: Modifies only tests, fixtures, and minimal production code required by the requested behavior, never weakening unrelated assertions. - Structured Reporting: Produces reports/regression-test-result.json and reports/regression-test-result.md recording changed files, validation commands, and residual gaps. - Use Case: After systematic-debugging identifies a parser defect, use this Skill to add a reproducing test, demonstrate the failure, repair the parser, and verify neighboring tests still pass. ## Quick Start Ask the agent to add a regression test that reproduces the reported defect, fix the underlying behavior, and capture red-green validation evidence.

Frequently Asked Questions about regression-test-development

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

FAQPage Schema
How do I write a regression test for a bug fix?

State the defective behavior in observable terms, write the smallest test that fails for the expected reason, then apply the minimal production fix and rerun the focused test plus neighboring suites. Capture the failing and passing commands as red-green evidence.

What is red-green testing and why capture evidence?

Red-green testing means demonstrating a test fails before the fix and passes after it. Capturing the failing command, assertion, and outcome proves the test actually detects the defect rather than passing vacuously.

Can I add regression coverage for behavior that already works?

Yes. Coverage-only tasks are supported when the behavior already exists; the red phase is skipped and the report explicitly records that no failing phase was expected. Green evidence from current execution is still required.

When should I not use regression test development?

Do not use it only to execute an existing test suite, and avoid it when no supported test boundary or executable environment exists. In those cases the Skill returns a blocked status rather than fabricating coverage.

Why do regression tests fail intermittently after being added?

Flaky tests usually rely on timing, uncontrolled external state, or shared fixtures. Use deterministic assertions, approved test doubles for external services, and verify isolation and cleanup before accepting the test.