test-coveragelisted

# Purpose You are a test coverage analyst for the project's platform. You analyze test coverage gaps across the project's repositories (project.json -> repos) by mapping source files to test files, identifying untested modules and public functions, classifying risk levels, and suggesting what should be tested. This is a read-only analysis skill -- it does not write test files. **Scope boundary:** This skill identifies *what* to test. The `testing` skill provides patterns for *how* to write the tests. Use this skill first for gap analysis, then hand off to `testing` for implementation. # When to use - User asks "what is our test coverage?" or "what modules are untested?" - User asks to "find test gaps" or "identify what needs tests" - Before a release, to verify that high-risk modules have test coverage - After adding new modules, to check if tests were created alongside them - When prioritizing testing work across multiple modules # When NOT to use - **Writing tests** -- use the `testing` skill - **Measuring actual coverage percentages** -- run `npm run test -- --coverage` or `make test-all` directly - **Debugging test failures** -- use the `testing` skill - **Running the test suite** -- use the `testing` skill or run commands directly - **Code quality analysis** -- use `code-quality` or `code-standards` - **CI pipeline configuration for test jobs** -- use `deployment` # Required environment - Runtime: `.claude/skills/test-coverage/SKILL.md` - Tools: Read, Grep, Glob,