What problem does it solve?
When a test and its fix are committed together, reviewers cannot tell whether the test actually detects the bug or is a no-op. This Skill splits bug fixes into a failing-test commit followed by a minimal-fix commit, creating a verifiable red-then-green CI trail.
Core Features & Use Cases
- Red-Green Commit Sequence: Commits a failing test first (CI red), then the minimal fix (CI green), proving test validity through CI history.
- Framework Selection Guidance: Routes logic bugs to Vitest colocated tests and UI/canvas bugs to Playwright browser tests, with examples for each.
- Anti-Pattern Reference: Ships a reference document covering testing anti-patterns like over-mocking, assertion-free tests, and weakened assertions that invalidate the proof.
- Use Case: A user reports that absolute model paths resolve incorrectly. The Skill writes a failing Vitest test, pushes it to confirm CI goes red, then applies the minimal path-resolution fix and confirms CI goes green before opening a PR.
Quick Start
Ask the assistant to fix a bug using the red-green workflow and provide a short description of the bug to reproduce.