- Installs
- 88
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/owainlewis/blueprint --skill coverage- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads coverage automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Coverage
Role
You are a test-focused engineer adding high-value coverage for real risk. Improve confidence without changing production behavior or chasing coverage numbers.
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.
FAQ
What does the coverage skill do?
Evaluate test coverage and fill real gaps with high-value tests.
How do I install coverage?
Run npx skills add https://github.com/owainlewis/blueprint --skill coverage in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/coverage/ (personal) or .claude/skills/coverage/ (project).
Which AI agents can use coverage?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is coverage safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains coverage?
It is published by owainlewis in owainlewis/blueprint. It has 88 recorded installs.
More from owainlewis/blueprint
review
owainlewis/blueprint
Uses a fresh agent to review an implementation change without editing it. Checks behavior, security, regressions, complexity, tests, docs, and missing proof. Use for code, PR, diff, security, second-opinion, or pre-merge reviews.
plan
owainlewis/blueprint
Turns a reviewed spec or decided brief into ordered tasks for separate agent runs. Use for implementation tasks, tracker tickets, or useful milestones. Do not use for one coding task or its short execution outline.
task-to-pr
owainlewis/blueprint
Open the skill to read its SKILL.md instructions.
spec
owainlewis/blueprint
Open the skill to read its SKILL.md instructions.
refactor
owainlewis/blueprint
Open the skill to read its SKILL.md instructions.
Popular testing & qa skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
grilling
mattpocock/skills
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
migrate-to-shoehorn
mattpocock/skills
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
run-train
lllllllama/rigorpilot-skills
Rigor Train skill for deep learning research repositories. Use when a documented or selected training command should be run conservatively for startup verification, short-run verification, full kickoff, or resume, with command, config, seed, log, checkpoint, status, and metric evidence written to standardized trainoutputs/. Do not use for environment setup, exploratory sweeps, speculative idea implementation, or end-to-end orchestration.
test-driven-development
obra/superpowers
Use when implementing any feature or bugfix, before writing implementation code
finishing-a-development-branch
obra/superpowers
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work