supercov
Helps your agent check code quality with tests. It measures the coverage of existing code and suggests new tests. It ensures the software works correctly.
What it does
This tool helps find parts of your code that aren't being tested. It then writes new, focused tests to cover those missing parts, improving your software's quality.
When to use it
- ✓When you want to add or improve existing tests.
- ✓When you want to know which code parts are untested.
- ✓When you want to increase your project's test coverage.
Example of what to ask your AI
“Find which parts of my code aren't being tested and write a test for the first one.”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
First, the tool runs all your current tests to see what's missing. Then, it identifies a small piece of untested code and writes a new, specific test for it. Finally, it runs everything again to show the improvement.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add sickn33/agentic-awesome-skills --skill supercovOr download just the file:
curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/supercov/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
Supercov
Overview
Supercov runs the project's own test command on the user's machine and reports line, branch and MC/DC coverage per test. It changes no source, tests or configuration. This skill uses that report to pick one untested piece of code at a time and write a focused test for it.
It works with JavaScript, TypeScript, Python, Ruby, Rust, Go, Java and Kotlin projects.
When to Use This Skill
- Use when the user asks to add or improve tests.
- Use when the user asks which code is untested, or asks to raise coverage.
- Use when the user asks which file to refactor first and has agreed to a quality check (see "Quality check").
Preconditions
- Node.js 22 or newer. If it is missing, tell the user. Do not install software without the user's approval.
- The project's test command, for example
npm test,pytestorcargo test. Ask if it is not obvious from the repository. - Always run the pinned version,
npx supercov@3.0.4. The first run downloads that release from npm, so get the user's approval before it.
How It Works
Step 1: Measure the suite
Run the full test command under Supercov. Coverage is measured locally and sends nothing over the network.
npx supercov@3.0.4 -- npm test
Step 2: Pick a target
List the untested code, pick one item, and read it in context.
npx supercov@3.0.4 runs latest gaps --limit 5
npx supercov@3.0.4 runs latest file src/session.js
Step 3: Write one focused test
Write one test for the chosen target. Change only test files unless the user asks otherwise.
Step 4: Rerun and report
Rerun the command from step 1. Report the test you added and the coverage before and after.
For anything not shown here, npx supercov@3.0.4 docs <topic> prints the guide for that version. Topics: agent-loop, quality, supported-suites, troubleshooting.
Examples
Example 1: Add a test for untested code
npx supercov@3.0.4 -- npm test
npx supercov@3.0.4 runs latest gaps --limit 5
# add one test for the first gap, then:
npx supercov@3.0.4 -- npm test
Example 2: Other languages
npx supercov@3.0.4 -- pytest
npx supercov@3.0.4 -- cargo test
npx supercov@3.0.4 -- go test ./...
npx supercov@3.0.4 -- ./gradlew test
Quality check
npx supercov@3.0.4 quality ranks files by code smells, and npx supercov@3.0.4 quality patch reports what a change introduced.
- These two commands send the project's source files to TypeSafe's API for analysis. Run them only when the user asked for a quality check, and tell the user before running that their source files will be sent to TypeSafe.
- They need the user's own
TYPESAFE_API_KEYin the environment. Never ask the user to paste a key into the conversation, and never create, read or print one. - If the key is missing, tell the user the check needs it, then answer from reading the code and say Supercov did not check it.
Best Practices
- ✅ Measure the full suite first, so the gaps reflect every test.
- ✅ Add one test per gap and rerun before picking the next.
- ✅ Report coverage before and after with the numbers Supercov printed.
- ❌ Don't change application code to raise coverage unless the user asks.
- ❌ Don't run the quality commands without the user's request and consent.
Limitations
- Coverage shows which code ran under a test. It does not show that the test checked the result.
- Supercov measures the suites listed in
npx supercov@3.0.4 docs supported-suites. Other runners are not measured. - The test command runs as the project defines it. If the suite needs services, credentials or network access, those needs still apply.
- This skill does not replace environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, or safety boundaries are missing.
Security & Safety Notes
- The skill runs the project's own test command and writes test files in the user's repository. Run it only in a repository the user has authorized, and keep changes to test files unless the user asks otherwise.
- Supercov writes its run data to a
.supercovdirectory in the project. It does not edit source, tests or configuration. npx supercov@3.0.4downloads a pinned release from the npm registry. Get the user's approval before the first run. Upgrading the pin needs a new review.
…
FAQ
Do I need to install anything?
The tool uses a command called `npx` which downloads and runs the latest version automatically. The first time, it will ask for your permission to download.
Does it change my main code?
No, it only creates new test files or modifies existing test files. Your main code is not changed.
Does it work with any programming language?
It works with JavaScript, TypeScript, Python, Ruby, Rust, Go, Java, and Kotlin.
Details
Original description by the author
Measure line, branch and MC/DC coverage of a project's existing tests with the supercov CLI, then write small, focused tests for the code no test reaches.
Popularity
- GitHub stars
- 48k
- Ranking position
- #4288
- License
- MIT
- Updated
- 10/15/2026
Comments
- …
More skills from this repository
00-andruia-consultant
Helps your agent start or improve AI projects. It analyzes code, suggests tools, and creates action plans in Spanish.
sickn33/agentic-awesome-skills
007
Lets your agent perform security audits and threat modeling. It's useful for protecting projects against attacks and vulnerabilities.
sickn33/agentic-awesome-skills
10-andruia-skill-smith
Helps your agent create or improve AI tools. It defines how tools work, writes documentation, and validates the structure.
sickn33/agentic-awesome-skills
20-andruia-niche-intelligence
Lets your agent create a summary about a specific industry. It's useful for understanding the context, rules, usage patterns, and risks of a project, using reliable sources.
sickn33/agentic-awesome-skills
Similar skills
cpp-testing
Makes your agent write and improve tests for C++ code. It helps set up testing tools and fix errors.
affaan-m/ECC
csharp-testing
Helps your agent create tests for C# and .NET code. It uses best practices to ensure tests are efficient and reliable.
affaan-m/ECC
django-tdd
Enables your agent to apply testing strategies for Django with pytest-django and TDD. It's useful for writing robust tests and ensuring code quality, especially for DRF APIs.
affaan-m/ECC