test-enforcement
Automated test validation, coverage checking, and quality metrics with aggressive defaults
Best use case
test-enforcement is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Automated test validation, coverage checking, and quality metrics with aggressive defaults
Teams using test-enforcement should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/test-enforcement/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How test-enforcement Compares
| Feature / Agent | test-enforcement | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Automated test validation, coverage checking, and quality metrics with aggressive defaults
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# 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
Related Skills
vitest
Vitest configuration, mocking, coverage, snapshot testing, and performance.
react-testing-library
React Testing Library patterns, queries, user events, and accessibility testing.
load-test-generator
Generate load test scripts for k6, Locust, and Gatling from OpenAPI specs
cloud-security-testing
Multi-cloud security assessment and penetration testing capabilities. Execute Prowler/ScoutSuite assessments, analyze IAM policies, identify cloud misconfigurations, test permissions, and enumerate cloud resources across AWS/GCP/Azure.
contract-test-framework
Consumer-driven contract testing for SDK-API compatibility. Generate Pact consumer tests, verify provider contracts, configure Pact broker, and implement can-i-deploy checks.
compatibility-test-matrix
Multi-version, multi-platform SDK compatibility testing
test-data-generation
Synthetic test data generation and management using Faker.js and similar tools. Generate realistic test data, create data factories, implement database seeding, and manage test data anonymization.
Stryker Mutation Testing
Stryker mutation testing for assessing test suite quality and effectiveness
pytest Testing
Expert pytest framework for Python unit, integration, and functional testing
Playwright E2E Testing
Deep integration with Playwright for browser automation and end-to-end testing
Percy Visual Testing
Percy visual testing platform integration for visual regression detection
pact-contract-testing
Consumer-driven contract testing with Pact framework. Generate consumer contracts, configure Pact Broker publishing, execute provider verification, detect breaking changes, and integrate with CI/CD pipelines.