What is coverage-review?

A read-only review that examines a project's test coverage, meaning which parts of the code are exercised by automated tests. It identifies uncovered areas and reports the findings before any code is changed.

Use it to inspect coverage in JavaScript, TypeScript, Python, Go, Rust, Java, Kotlin, Ruby, Elixir, or PHP projects and receive a report of gaps. It also checks which test and coverage tools the project uses.

It shows where tests are missing without making unapproved edits, helping you decide what should be tested next.

coverage-review — Skill for Claude Code by eugeniosegala

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 eugeniosegala/claude-connoisseur --skill coverage-review

Clone the repo

git clone --depth 1 https://github.com/eugeniosegala/claude-connoisseur

Made for: Claude Code.

Or install claude-connoisseur, the plugin that ships this one along with the rest of its 13 skills, 2 hooks.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/eugeniosegala/claude-connoisseur/coverage-review/github.svg)](https://agentmods.dev/skills/eugeniosegala/claude-connoisseur/coverage-review)

Your own site

<a href="https://agentmods.dev/skills/eugeniosegala/claude-connoisseur/coverage-review"><img src="https://agentmods.dev/badge/skills/eugeniosegala/claude-connoisseur/coverage-review/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/eugeniosegala/claude-connoisseur/coverage-review"><img src="https://agentmods.dev/badge/skills/eugeniosegala/claude-connoisseur/coverage-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,678 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.

Model	Per session	Once invoked
Fable 5.1	$0.00015	$0.01678
Opus 5	$0.00008	$0.00839
Sonnet 5	$0.00003	$0.00336
Haiku 4.5	$0.00002	$0.00168

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

Security

Grade A, and why

coverage-review 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.

skills/coverage-review/SKILL.md · 158 lines

How it starts

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

Coverage Review

Analyse the project's test coverage, identify gaps, and present an assessment for the user to review before any changes are made. Do not write or modify any code until the user provides next steps.

Files and instructions: $ARGUMENTS

What to detect

Before running anything, determine the test framework, runner, and coverage tooling by inspecting the project:

JavaScript/TypeScript: jest --coverage, vitest --coverage, c8, nyc/istanbul — check package.json scripts, config files, and dev dependencies for coverage providers (@vitest/coverage-v8, @vitest/coverage-istanbul, c8, nyc)
Python: pytest --cov, coverage.py — check pyproject.toml, setup.cfg, .coveragerc
Go: go test -cover, go test -coverprofile — built-in
Rust: cargo tarpaulin, cargo llvm-cov — check Cargo.toml dev-dependencies
Java/Kotlin: jacoco, cobertura — check pom.xml or build.gradle plugins
Ruby: simplecov — check Gemfile
Elixir: mix test --cover, excoveralls — check mix.exs
PHP: phpunit --coverage-text — check phpunit.xml, composer.json

If no coverage tool is installed, recommend one appropriate for the detected framework and ask the user before installing it.

How to interpret arguments

The arguments are free-form and flexible. They may contain:

File or directory references to scope the analysis: src/services/, @auth.ts, lib/, *.py
Natural language instructions such as:
- "focus on the API layer"
- "only check the utils module"
- "ignore generated files"
- "include integration tests"

When no arguments are provided, analyse coverage for the entire project.

Examples

/coverage-review — full project coverage analysis
/coverage-review src/services/ — coverage for a specific directory
/coverage-review @auth.ts — coverage for a specific file
/coverage-review focus on the API handlers — scoped by description
/coverage-review ignore generated files and vendor/ — with exclusions

Read the full file on GitHub · 158 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.

12d ago First seen · 158 lines · 15 tokens per session scan A 41f1fead6626

Subscribe to this mod's changes

coverage-review is a skill published in the GitHub repository eugeniosegala/claude-connoisseur (9 stars, last pushed 4mo ago), licensed MIT. It adds 15 tokens to every session and 1,678 once invoked, about $0.0001 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-31.

Testing

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

coverage-review