Automated test validation, coverage checking, and quality metrics with aggressive defaults
Scanned 5/29/2026
Install to Claude Code
npx -y skills add a5c-ai/babysitter --skill test-enforcement --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Test Enforcement?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/a5c-ai-test-enforcement)More formats (shields.io, HTML) on the badges page.
---
name: test-enforcement
description: Automated test validation, coverage checking, and quality metrics with aggressive defaults
allowed-tools: [Read, Write, Edit, Bash, Grep, Glob]
---
# 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
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...