Select Happier test lanes and enforce fixture guardrails in TDD workflows.
npx skills add https://github.com/happier-dev/happier --skill happier-testing
Please help me install this Agent Skill. Skill: happier-testing Source: https://github.com/happier-dev/happier/tree/main/skills/happier-testing Command: npx skills add https://github.com/happier-dev/happier --skill happier-testing
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.
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.
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.
High-intent search queries and answers about installing and using this skill.
Enforce TDD by selecting the smallest relevant test slice using Happier's canonical lane map, then following tight RED-GREEN-REFACTOR loops with fixture and mock guardrails. This prevents broken shared contracts and reduces unnecessary builds and infra noise.
Failure classification guardrails distinguish production bugs from test drift, harness drift, and infra or resource issues. This ensures fixes land in the correct layer, preventing outdated fixtures or harnesses from masking real regressions.
Prevent stale fixture drift by applying fixture and mock guardrails alongside an inventory-first impact scoping step. This workflow ensures that changes to shared helpers or wiring points update the correct tests without masking real regressions.
Anti-flake validation discipline handles flaky tests by allowing only one active rerun per spec or lane. When shared helpers change, broader reruns are triggered to catch leaked handles or cleanup regressions across the affected test lanes.
Test-driven development supports database contract testing and provider scenarios by applying lane-aware test selection and fixture guardrails. The workflow covers behavior-changing work across integration, e2e core, providers, and database contracts while minimizing infra noise.
mori-shin-xCalculate forward propagation from files or symbols to affected requirements, documentation, and tests.
48Nauts-OperatorImplement a Test-Driven Development workflow with RED-GREEN-REFACTOR cycles.
JOHNNYWHITEMIKECompare V8 heap snapshots across time within the same Vitest worker PID to diagnose test-induced heap growth and worker OOM risk.
Patasse97Generate tests, analyze coverage, and guide RED-GREEN-REFACTOR workflows across languages.
