Stats
Actions
Tags
From testing
Check code coverage and use mutation testing to verify test quality.
How this command is triggered — by the user, by Claude, or both
Slash command
/testing:validate-coverage coverage-report or code-fileThe summary Claude sees in its command listing — used to decide when to auto-load this command
Chain these steps: 1. Use the `test-doubles-strategy` skill to verify mocks are appropriate 2. Use the `mutation-testing` skill to measure test effectiveness 3. Use the `unit-test-design` skill to strengthen tests for uncaught mutations 4. Synthesize into coverage report with recommended test additions After completion, suggest: "Run mutation tests locally to validate these improvements."
Chain these steps:
test-doubles-strategy skill to verify mocks are appropriatemutation-testing skill to measure test effectivenessunit-test-design skill to strengthen tests for uncaught mutationsAfter completion, suggest: "Run mutation tests locally to validate these improvements."
npx claudepluginhub sethdford/claude-skills --plugin engineer-testing/test-coverageAnalyzes test coverage using tools for JavaScript, Python, Java, C#, Ruby; generates reports, identifies gaps, and recommends new tests.
/mutation-testingRuns mutation testing (Stryker/pitest/mutmut) on source files/modules, triages surviving mutants via AI, and writes killing tests. Asks for approval first.
/mutateRuns mutation testing on source files with Stryker (JS/TS), mutmut (Python), or PITest (Java), computes mutation score, lists survived mutants with test suggestions, saves report.
/mutateRuns mutation testing to verify test quality by building a custom mutation tool or using an existing framework, then reports mutation score and surviving mutants.
/coverageAnalyzes test coverage for projects or specific files/directories, generates markdown report with metrics, directory breakdowns, low-coverage files, uncovered lines, and prioritized test recommendations. Supports --target flag.