Skip to content

Skill

Reviewing Test Coverage

Audits existing tests against the features, behavior, requirements, or implementation they should cover.

Back to Skills

When to use

Audits existing tests against the features, behavior, requirements, or implementation they should cover - classifying coverage per feature as Covered, Weakly covered, Not covered, or Not assessable, and reporting weak assertions, fixture, mock, and setup problems, and missing scenarios as coverage gaps.

  • Use when

    Use when the question is whether existing tests adequately cover specified behavior.

  • Limits

    Does not write tests, analyze broader regression risk, or produce a remediation plan.

Skill package

SKILL.md

This Skill is a single file. The download is its SKILL.md, with the complete frontmatter and instructions.

  • reviewing-test-coverage/SKILL.md

Inputs required

Test basis
The features, behavior, requirements, or implementation evidence that define what should be tested.
Existing tests
Test files or excerpts, assertions, fixtures, mocks, setup, cleanup, and test data.

Access needed

Needs read access to the tests and to the behavior, requirements, or implementation they should cover (repository or pasted excerpts). Running tests or coverage tools is optional, requires command-execution permission, and is done only when the user asks. Does not modify files.