mkl-write-regression

Write focused regression tests that fail on the affected version before a fix.

11|1|Updated Sep 13, 2026
One-click install
npx skills add https://github.com/00200200/maintainer-skills-lab --skill mkl-write-regression-00200200
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mkl-write-regression
Source: https://github.com/00200200/maintainer-skills-lab/tree/main/providers/cursor/.cursor/skills/mkl-write-regression
Command: npx skills add https://github.com/00200200/maintainer-skills-lab --skill mkl-write-regression-00200200

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Bug fixes often ship without a test that proves the defect existed, or with tests that mirror the implementation instead of the public behavior. This Skill guides the creation of a minimal regression test derived from an established reproduction, so the test fails on the affected version and passes after the fix. ## Core Features & Use Cases - Behavior-Driven Assertions: Derives assertions from the public behavior a caller needs, not from the proposed implementation, avoiding tests that mirror internal logic. - Baseline Verification: Instructs running the test against the affected implementation (or an isolated pre-fix checkout) and interpreting failures, distinguishing real behavioral evidence from import errors, timeouts, or collection failures. - Working Tree Safety: Preserves the user's current checkout and uncommitted work, using isolated checkouts instead of reverting the working tree to get a red test. - Use Case: After reproducing a slug-generation bug where punctuation is mishandled, use this Skill to write a small deterministic test asserting the expected punctuation and whitespace behavior, confirm it fails on the pre-fix version, and report the baseline and fixed-version results. ## Quick Start Ask the AI to write a regression test from the existing bug reproduction, verify it fails on the affected version, and report the baseline and fixed-version results.

Frequently Asked Questions about mkl-write-regression

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?▼

Start from the bug reproduction and the expected public behavior, then write the smallest test asserting that behavior with deterministic inputs. Run it against the affected version to confirm it fails for the right reason before accepting it.

How to verify a regression test fails before the fix?▼

Run the test against the affected implementation or an isolated pre-fix checkout. Confirm the failure is an assertion about the reported behavior, not an import error, collection failure, permission problem, or timeout.

Should a regression test mirror the implementation code?▼

No. Assertions should derive from the behavior a caller needs, not from the proposed implementation. Mirroring internal transformation steps produces brittle tests that pass or fail for the wrong reasons.

Can I get a failing test without reverting my working tree?▼

Yes. Use an isolated checkout or an equivalent preserved baseline of the pre-fix version. This keeps your current checkout and uncommitted work intact while still producing a red test on the affected code.

When is a failing test not valid regression evidence?▼

A failure caused by import errors, collection failures, permission problems, or timeouts is not evidence of the bug. Only an assertion failure about the reported behavior proves the test captures the defect.