test-coverage-check

test-coverage-check is a skill for Claude Code from davila7/claude-with-skills. It costs 34 tokens per session (643 once invoked), scanned A, original, MIT.

A check that looks for test files corresponding to changed source files. Tests are code that verify whether other code behaves as expected.

In plain words
What is it for?
Use it during code review or before merging to identify changed source files that may lack matching test coverage.
Why use it?
It can reveal changed production code that has no nearby or conventionally named tests before a pull request is merged.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: agent in frontmatter.

Good fit Use it during code review or before merging to identify changed source files that may lack matching test coverage.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/davila7/claude-with-skills/test-coverage-check
About the project

Claude With Skills is a progressive course that teaches developers to create reusable, portable Agent Skills for Claude Code, from basic SKILL.md files to advanced automation and plugin packaging. It is intended for developers who want repeatable instructions and workflows instead of repeatedly pasting the same guidance. The catalogue contains the course's skills, agents, and instruction.

davila7/claude-with-skills · 12 stars · on GitHub · claude-with-skills.vercel.app

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add davila7/claude-with-skills --skill test-coverage-check
Clone the repo
git clone --depth 1 https://github.com/davila7/claude-with-skills

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for test-coverage-check

README.md
[![agentmods](https://agentmods.dev/badge/skills/davila7/claude-with-skills/test-coverage-check/github.svg)](https://agentmods.dev/skills/davila7/claude-with-skills/test-coverage-check)
Your own site
<a href="https://agentmods.dev/skills/davila7/claude-with-skills/test-coverage-check"><img src="https://agentmods.dev/badge/skills/davila7/claude-with-skills/test-coverage-check/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for test-coverage-check

Your own site · 80×15
<a href="https://agentmods.dev/skills/davila7/claude-with-skills/test-coverage-check"><img src="https://agentmods.dev/badge/skills/davila7/claude-with-skills/test-coverage-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 643 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00034 $0.00643
Opus 5 $0.00017 $0.00321
Sonnet 5 $0.00007 $0.00129
Haiku 4.5 $0.00003 $0.00064

Measured 12d ago against content hash cb11e084246b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

test-coverage-check scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

src/content/docs/03-advanced/capstone/solution/.claude/skills/test-coverage-check/SKILL.md · 68 lines

How it starts

The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Check whether changed source files have test coverage.

Changed source files

!git diff --name-only HEAD~1 2>/dev/null || git diff --name-only origin/main...HEAD 2>/dev/null || echo "none"

Filter the list above to source files only. Exclude:

  • Files already in test directories (test/, spec/, __tests__/, tests/)
  • Files with .test., .spec. in the name
  • Non-source files: .md, .json, .yaml, .yml, .lock, .txt, .env, .gitignore
  • Configuration files: *.config.ts, *.config.js, vite.config.*, jest.config.*

If the output was "none" or after filtering there are no source files, output: COVERAGE FINDINGS: none — no changed source files detected

Check each source file

For each changed source file, derive candidate test file paths using these conventions:

Given source file src/utils/parser.ts, check for:

  1. src/utils/parser.test.ts
  2. src/utils/parser.spec.ts
  3. src/utils/__tests__/parser.ts
  4. src/utils/__tests__/parser.test.ts
  5. tests/utils/parser.test.ts
  6. tests/utils/parser.spec.ts
  7. test/utils/parser.test.ts
  8. test/utils/parser.spec.ts

Apply the same pattern for .py, .js, .jsx, .tsx, .go, .rb files, substituting the appropriate test file extension:

  • Python: _test.py or test_<name>.py
  • JavaScript/TypeScript: .test.js, .spec.js, .test.ts, .spec.ts
  • Go: _test.go in the same directory
  • Ruby: _spec.rb in spec/

Use Glob to check whether any of the candidate paths exist.

If a test file is found, use Grep to check whether it imports or requires the source file, or references the source file's name. If no import is found, mark as "test file exists but may not cover new changes".

Output format

Output exactly:

COVERAGE FINDINGS:
- <source-file> — no test file found
- <source-file> — test file exists but may not cover new changes

Examples:

COVERAGE FINDINGS:
- src/auth/loginHandler.ts — no test file found
- src/utils/formatDate.ts — test file exists but may not cover new changes

Read the full file on GitHub · 68 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 68 lines · 34 tokens per session scan A cb11e084246b

Subscribe to this mod's changes

test-coverage-check is a skill published in the GitHub repository davila7/claude-with-skills (12 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 643 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens

atmos-validation

Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.

cloudposse/atmos · 31 tokens

skill-benchmark

Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.

HoangNguyen0403/agent-skills-standard · 16 tokens