test-enforcement
Automated test validation, coverage checking, and quality metrics with aggressive defaults
npx skills add a5c-ai/babysitter --skill test-enforcement --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Test Enforcement ## Capabilities Validates automated tests, checks coverage against thresholds, and reports quality metrics. Implements Maestro's "turn checks up to 11" philosophy with aggressive lint and test defaults. ## Tool Use Instructions - Use **Bash** to run test suites, lint, and coverage commands - Use **Read** to examine test files and coverage reports - Use **Grep** to find untested code paths and missing test files - Use **Glob** to verify test file naming conventions - Use **Write** to generate coverage reports and test suggestions ## Process Integration - Used across all Maestro processes for test verification - Used in `maestro-maintenance.js` (Coverage gap analysis) - Agents: Test Engineer, Coder (test writing) - Enforces: unit tests, integration tests, lint, format - Coverage thresholds configurable per project - "Turn checks up to 11" default behavior
- Capabilities
- Tool Use Instructions
- Process Integration
What does the test-enforcement skill do?
Automated test validation, coverage checking, and quality metrics with aggressive defaults
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill test-enforcement --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.