Verify test coverage

Skill matusbu/claude-code-test-automation-skills/.claude/skills/verify-test-coverage

Reusable Claude Code skills for test automation workflows

Install

npx -y skills add matusbu/claude-code-test-automation-skills --skill verify-test-coverage

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Verify test coverage for code changes against the defined test strategy. Use when reviewing a feature branch, commit, or uncommitted changes to ensure adequate test coverage.

SKILL.md

2.4 KB, 458 tokens by cl100k_base, as published. Nobody here has run it

Verify Test Coverage

Analyze test coverage for code changes and identify gaps based on the test strategy.

Step 1: Detect scope of change

The scope defines which code changes to analyze for test coverage.

Scope options:

If $scope is "uncommitted" or "unstaged": analyze uncommitted changes (git diff HEAD)
If $scope is "last-commit": analyze the most recent commit (git diff HEAD~1 HEAD)
If $scope matches pattern "last-N-commits": analyze last N commits from HEAD
If $scope is empty or "branch": analyze diff between current feature branch and main (git diff main...HEAD)
If $scope is a custom git range (e.g., "commit1..commit2"): use that range
If $scope is unclear or not provided, ask the user what scope they want to analyze

Determine the appropriate git command and execute it to get the diff.

Step 2: Locate test strategy

Look for the test strategy definition to understand what needs to be tested.

Strategy location:

First, check if TEST_STRATEGY.md exists in the repository root
If not found, check .claude/ directory for strategy documentation
If user mentioned a specific strategy in their prompt, use that instead
If no strategy file found, ask the user where the test strategy is defined

Step 3: Review current test coverage

Based on the code changes from Step 1 and test strategy from Step 2:

Identify what files were changed and what functionality was added/modified
Search for existing tests covering those changes
Compare existing test coverage against the test strategy requirements
Determine coverage according to the test levels defined in the strategy file

Step 4: Report results and gaps

Provide a summary:

Scope analyzed: what code changes were reviewed
Test coverage found: list existing tests covering the changes
Gaps identified: what's missing based on the test strategy
Recommendations: specific tests that should be added to close the gaps

If gaps exist, propose concrete test cases that need to be written.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most quality gates skills give in 458 tokens

Counted across 1,195 of the 2,094 authors here whose files we hold, read 2026-08-07

Read the output and check the exit codein 54 of 1195, across 14 files
Verify requirements using a line-by-line checklistin 53 of 1195, across 12 files
Identify the verification command proving the claimin 51 of 1195, across 12 files
Run the full verification commandin 50 of 1195, across 11 files
Verify output confirms the claimin 49 of 1195, across 12 files
Check version control diff after agent delegationin 46 of 1195, across 6 files
State claim with evidencein 44 of 1195, across 4 files
Run the test suitein 33 of 1195, across 26 files
Keep state in memory by defaultin 27 of 1195, across 6 files
Make prototype runnable with one commandin 26 of 1195, across 5 files
Produce a verification reportin 25 of 1195, across 14 files
Detect the package manager from lockfilesin 24 of 1195, across 5 files

Said here and by no other author read

execute git diff for the target scope
ask the user if scope is unclear
locate the test strategy file
ask the user if no strategy exists
identify changed functionality
search for existing tests

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.