happier-testing

What problem does it solve?

This Skill prevents Happier changes from drifting into broken shared contracts or stale fixtures by enforcing a strict RED-GREEN-REFACTOR workflow tailored to the repo’s test lanes and anti-flake rules.

Core Features & Use Cases

• Lane-aware TDD workflow: Chooses the smallest relevant test slice using Happier’s canonical lane map and setup files to avoid unnecessary builds and reduce noise.
• Failure classification guardrails: Distinguishes production bugs from test drift, harness drift, and infra/resource issues so fixes land in the right layer.
• Anti-flake validation discipline: Applies rerun discipline (only one active rerun per spec/lane) and broader reruns when shared helpers change to catch leaked handles or cleanup regressions.

Use case: You change a shared runtime contract or CLI/server/UI wiring point, and you need to update the right tests without letting outdated fixtures or harnesses mask real regressions.

Quick Start

Use the happier-testing skill when you modify Happier code that affects shared runtime contracts, CLI/server/UI flows, or any lane prone to stale fixtures, and follow the RED-GREEN-REFACTOR workflow with the lane map and fixture/mock policy.