Individual skill
test-enforcement
Automated test validation, coverage checking, and quality metrics with aggressive defaults
library/methodologies/maestro/skills/test-enforcement/SKILL.md
Source commit feb68abe397acc14f32b34984975c48fedba2b33
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,903
- Repository last updated
- Nov 1, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-orchestration Repository topic
- agent-skills Repository topic
- agentic-ai Repository topic
- agentic-workflow Repository topic
- ai-automation Repository topic
- babysitter Repository topic
- claude-code Repository topic
- claude-skills Repository topic
- trustworthy-ai Repository topic
- vibe-coding Repository topic
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# 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