What is test-coverage?

A test-coverage workflow that shows which parts of a selected code module are exercised by tests. Test coverage measures executed code, while uncovered lines and branches show potential gaps.

Run coverage for use-case, domain, or adapter modules, filter by class, list uncovered lines and branches, and map reachable gaps to test scenarios.

It helps find untested code after tests pass and can focus the report on recently changed classes.

How rakovi4/continue-framework configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to rakovi4/continue-framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/rakovi4/continue-framework/main/.claude/skills/test-coverage/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/rakovi4/continue-framework

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/rakovi4/continue-framework/test-coverage/github.svg)](https://agentmods.dev/skills/rakovi4/continue-framework/test-coverage)

Your own site

<a href="https://agentmods.dev/skills/rakovi4/continue-framework/test-coverage"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/test-coverage/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/rakovi4/continue-framework/test-coverage"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/test-coverage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 518 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00056	$0.00518
Opus 5.5	$0.00022	$0.00207
Sonnet 5.5	$0.00011	$0.00104
Haiku 4.5	$0.00006	$0.00052

Measured 1mo ago against content hash b8a5fedf2a2a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

test-coverage 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 1mo 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.

.claude/skills/test-coverage/SKILL.md · 54 lines

How it starts

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

/test-coverage - Run Tests with Coverage Report

Usage

/test-coverage usecase
/test-coverage storage
/test-coverage rest RegisterUserController
/test-coverage usecase --focus    # only classes touched in recent git diff

Arguments

First word is the module:

usecase → :usecase
storage, rest, email, scheduling, security → :adapters:{name}
domain → measured through the suites exercising domain code
frontend → frontend coverage tooling from the active technology profile

Optional second word filters the report to classes matching that name.

Optional --focus restricts the report to changed production files. In staged lanes, pass the recorded baseline and explicit owned paths, including already committed changes; use last-commit focus only when no explicit scope was supplied. Pass report-only mode for every staged lane so the coordinator owns tracking.

Action

Delegate to .claude/agents/coverage-agent.md with module, focus paths/baseline, and report-only mode. It resolves backend or frontend tooling from the active technology profile and uses .claude/templates/testing/coverage-commands.md for scope, report format, gap mapping, and remediation.

Steps:

Run tests with coverage (stop if tests fail)
Compute each touched module summary from its coverage report
List classes with gaps (apply filter/focus if specified)
Extract uncovered lines/branches, read source to show actual code
Report results
In --focus mode: map gaps to scenarios and classify reachability; return staged-lane findings to the coordinator, otherwise update progress.md for reachable gaps. Flag dead code for refactor.

Agent

.claude/agents/coverage-agent.md — workflow for gap analysis, reachability classification, progress.md updates

Templates

.claude/templates/testing/coverage-commands.md — universal workflow: focus mode, module mapping, report format
.claude/tech/{backend}/templates/testing/coverage-commands.md — tool-specific commands: run, parse, extract

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

1mo ago Changed · +7 lines b8a5fedf2a2a
2mo ago First seen · 47 lines · 56 tokens per session scan A a378dc18853d

Subscribe to this mod's changes

test-coverage is a skill published in the GitHub repository rakovi4/continue-framework (54 stars, last pushed 29d ago), licensed MIT. It adds 56 tokens to every session and 518 once invoked, about $0.0002 per session on Opus 5.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.

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

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

continue-framework: Skill for Claude Code