Code coverage

Skill viknesh20-20/claude-code-tool-kit/.claude/skills/code-coverage

Production-ready Claude Code configuration. 12 original agents, 200+ slash-command skills, 45+ MCP servers, 14 plugins, design + 3D + WebGPU + GSAP + RAG tooling. One-command Node.js installer for premium websites, SaaS apps, AI agents. Free, MIT, stack-agnostic.

Install

npx -y skills add viknesh20-20/claude-code-tool-kit --skill code-coverage

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Analyzes test coverage, identifies untested code paths, and generates tests for the most critical uncovered areas. Use to improve test coverage before releases.

SKILL.md

2.8 KB, as published. Nobody here has run it

Test Coverage Analysis

Detect Test Setup

Process

Step 1: Run Coverage (if configured)

Attempt to run the project's coverage command:

Ecosystem	Coverage Command
npm (Jest)	`npx jest --coverage --json 2>/dev/null`
npm (Vitest)	`npx vitest run --coverage 2>/dev/null`
npm (c8)	`npx c8 report --reporter=json 2>/dev/null`
Python (pytest)	`python -m pytest --cov --cov-report=json 2>/dev/null`
Go	`go test -coverprofile=coverage.out ./... 2>/dev/null && go tool cover -func=coverage.out`
Rust	`cargo tarpaulin --out json 2>/dev/null`

If coverage tools aren't configured, proceed with static analysis.

Step 2: Static Analysis (if no coverage tool)

For the target file(s):

Identify all public functions, methods, and classes
Search for corresponding test files
For each function, check if there's a test that calls it
Map which code paths (branches, error handlers) have test coverage

Step 3: Coverage Report

Summary

Metric	Value
Line coverage	XX%
Branch coverage	XX%
Function coverage	XX%
Uncovered files	X

Uncovered Critical Code

List the most important uncovered code, prioritized by:

Business logic — core features and workflows
Error handling — catch blocks, error paths, edge cases
Security-sensitive — auth, input validation, data access
Complex logic — functions with high cyclomatic complexity

For each uncovered area:

File path and line numbers
What the code does
Why it's important to test
Suggested test cases

Step 4: Generate Missing Tests

For the top 5 most critical uncovered areas, generate test code following the project's test patterns (same structure as /write-tests).

Step 5: Coverage Improvement Plan

Priority	File	Current	Target	Tests Needed
1	...	XX%	80%+	...
2	...	XX%	80%+	...

Rules

Focus on meaningful coverage, not 100% — test behavior, not implementation
Prioritize business logic and error paths over boilerplate
Don't generate tests just to increase numbers — each test should validate something valuable
Respect existing test patterns and conventions