Skill

coverage

Evaluates test coverage for files, modules, recent changes, or commits and adds high-value tests for real gaps like edge cases, failures, and integrations.

testing

npx claudepluginhub owainlewis/blueprint --plugin blueprint

Tool Access

This skill uses the workspace's default tool permissions.

Preview

- You want to check whether recent work is tested well enough

SKILL.md

Similar Skills

test-generation

Generates tests for new or existing code via structured workflow: analyzes paths/edge cases, creates tests, validates coverage goals.

1 file

nickcrew-claude-ctx-plugin

write-test

Guides coverage-driven test writing for existing codebases: discovers untested user-facing behavior via coverage reports, writes one meaningful test per iteration, marks low-value code with ignore annotations.

amplify

Unit Test Coverage Improvement

Discovers unit testing gaps and generates new tests following project conventions. Supports deep iterative mode and harness for automated multi-cycle coverage improvement.

3 files

optimus

Stats

Stars79

Forks18

Last CommitApr 20, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Coverage

When to use

You want to check whether recent work is tested well enough

A file or module looks fragile or under-tested

You want to add tests without changing behavior

Process

Choose the target from $ARGUMENTS, current changes, or the latest commit. If there is still no clear target, ask.

Read the code and the existing tests.

Identify realistic gaps: edge cases, failure paths, state changes, and integration points.

Add only the tests that would catch a real bug.

Run the relevant tests and confirm they pass.

Verification

The target area is clear

New tests cover real risk, not coverage vanity

The code under test was not changed

Tests pass

Rules

Focus on the smallest set of tests that meaningfully improves confidence.

Add coverage for contract and failure-path behavior before edge-case trivia.

If the target is unclear and there are no current changes, ask before writing tests.

Do not write tests just to raise a number.

Do not add tests for trivial code or framework behavior.

If the code is already well-tested, say so.

Coverage

When to use

You want to check whether recent work is tested well enough
A file or module looks fragile or under-tested
You want to add tests without changing behavior

Process

Choose the target from $ARGUMENTS, current changes, or the latest commit. If there is still no clear target, ask.
Read the code and the existing tests.
Identify realistic gaps: edge cases, failure paths, state changes, and integration points.
Add only the tests that would catch a real bug.
Run the relevant tests and confirm they pass.

Verification

The target area is clear
New tests cover real risk, not coverage vanity
The code under test was not changed
Tests pass

Rules

Focus on the smallest set of tests that meaningfully improves confidence.
Add coverage for contract and failure-path behavior before edge-case trivia.
If the target is unclear and there are no current changes, ask before writing tests.
Do not write tests just to raise a number.
Do not add tests for trivial code or framework behavior.
If the code is already well-tested, say so.