author-regression-test

Generate a YAML regression-test artifact from rca.yaml and design.yaml.

3|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/kapilvirenahuja/garura --skill author-regression-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: author-regression-test
Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/skills/author-regression-test
Command: npx skills add https://github.com/kapilvirenahuja/garura --skill author-regression-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you author true regression tests that fail on the unfixed code and pass only after the intended fix, preventing accidental “already-green” tests that don’t protect against the defect.

Core Features & Use Cases

  • Red-before-green enforcement: verifies the derived assertion is failing against the current codebase before writing the regression test file.
  • Defect-to-assertion derivation: turns RCA and fix design into a specific, mechanical assertion using grep, glob, file-shape checks, or unit-test commands.
  • YAML eval-spec regression artifact authoring: generates a structured regression-test.yaml including expected red/green states and metadata for later execution.

Quick Start

Ask the agent to run author-regression-test with the paths to your rca.yaml and design.yaml, your project_root, and an output_base to write regression-test.yaml.

Frequently Asked Questions about author-regression-test

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

FAQPage Schema
How do I write a regression test that fails before the fix and passes after?

Regression tests that enforce red-before-green verify the derived assertion is failing against the current codebase before writing the test file. This prevents accidental already-green tests that do not protect against the defect.

How do I derive a mechanical assertion from root-cause analysis for TDD?

Deriving a mechanical assertion from RCA turns root-cause analysis and fix design into specific assertions using grep, glob, file-shape checks, or unit-test commands. This ensures the regression test is observable and deterministic.

What is a YAML eval-spec for regression testing?

A YAML eval-spec for regression testing is a structured regression-test.yaml artifact that includes expected red and green states along with metadata for later execution. It captures the defect and proves the fix causes a red-to-green state transition.

How do I generate regression test artifacts from rca.yaml and design.yaml?

You generate regression test artifacts by providing the paths to your rca.yaml and design.yaml, your project_root, and an output_base. The workflow authors a regression-test.yaml file that verifies the fix causes a red-to-green state transition.

Why do my regression tests pass before I apply the fix?

Regression tests that pass before applying the fix are accidental already-green tests that fail to protect against the defect. Red-before-green enforcement verifies the derived assertion is failing against the current codebase before writing the test.

Can I use grep assertions for deterministic verification in regression testing?

Grep assertions are supported for deterministic verification in regression testing. The defect-to-assertion derivation process turns root-cause analysis into specific mechanical assertions using grep, glob, file-shape checks, or unit-test commands.