Who it is forA developer opening a pull request who wants a reviewer to see the coverage evidence without rerunning the tests.
The problemReviewers often have no easy way to see what a change covered, and raw terminal output is hard to share.
The outcomeA single private report file, stored under .supercov/reports/, that opens in a browser and compares the latest run with the previous snapshot.
What you need first
- A project with a complete test command the repository already runs, such as npm test, pytest or cargo test
- Node.js so npx can fetch Supercov, or one of the other install routes in the README
- A TypeSafe AI API key from https://typesafe.ai, only for quality and security scoring; coverage needs no account
Steps
- Run
npx supercov -- npm testto record a complete run with the test command your repository uses. - Run
npx supercov reportto generate one private, interactive report file. - Find the generated file in
.supercov/reports/, which the store's own .gitignore keeps out of git. - Attach that single file to your pull request so a reviewer can download it and open it in a browser.
Prompt for your agent
In the repository at <project path>, run `npx supercov -- <test command>` and then `npx supercov report`. Report the path of the file created under .supercov/reports/ and confirm that the file is not tracked by git.
Caveat. The report is written as a file you attach yourself, since the README describes no hosted sharing, so the reviewer receives a copy of the file rather than a live link.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for supercorp-ai/supercov and "Attach a private coverage report to a pull request"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer