Requirements
rizsotto/Bear
Write, modify, or review a requirement file under docs/requirements -- pick the single owning file, keep the text contract-only, name IDs so they need no explanation, and verify cross-references and…
Regenerate the coverage report and badges, or diagnose a wrong percentage, a 404ing badge, or a package showing 0%.
Install Coverage Report
$ npx skills add petarzarkov/dunx --skill coverage-report -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install petarzarkov/dunx coverage-report --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/petarzarkov/dunx.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/coverage-report .claude/skills/coverage-report && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "coverage-report" agent skill from https://github.com/petarzarkov/dunx/tree/main/.claude/skills/coverage-report into .claude/skills/coverage-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coverage-report", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/petarzarkov/dunx/tree/main/.claude/skills/coverage-reportType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add petarzarkov/dunx --skill coverage-report -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install petarzarkov/dunx coverage-report --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/petarzarkov/dunx.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/coverage-report .agents/skills/coverage-report && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "coverage-report" agent skill from https://github.com/petarzarkov/dunx/tree/main/.claude/skills/coverage-report into .agents/skills/coverage-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coverage-report", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add petarzarkov/dunx --skill coverage-report -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install petarzarkov/dunx coverage-report --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/petarzarkov/dunx.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/coverage-report .cursor/skills/coverage-report && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "coverage-report" agent skill from https://github.com/petarzarkov/dunx/tree/main/.claude/skills/coverage-report into .cursor/skills/coverage-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coverage-report", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/petarzarkov/dunx.git --path .claude/skills/coverage-report--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add petarzarkov/dunx --skill coverage-report -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install petarzarkov/dunx coverage-report --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/petarzarkov/dunx.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/coverage-report .gemini/skills/coverage-report && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "coverage-report" agent skill from https://github.com/petarzarkov/dunx/tree/main/.claude/skills/coverage-report into .gemini/skills/coverage-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coverage-report", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install petarzarkov/dunx coverage-reportInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add petarzarkov/dunx --skill coverage-report -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/petarzarkov/dunx.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/coverage-report .github/skills/coverage-report && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "coverage-report" agent skill from https://github.com/petarzarkov/dunx/tree/main/.claude/skills/coverage-report into .github/skills/coverage-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coverage-report", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add petarzarkov/dunx --skill coverage-report -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install petarzarkov/dunx coverage-report --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/petarzarkov/dunx.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/coverage-report .opencode/skills/coverage-report && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "coverage-report" agent skill from https://github.com/petarzarkov/dunx/tree/main/.claude/skills/coverage-report into .opencode/skills/coverage-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coverage-report", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
coverage-report- GitHub stars
- 100
- Token cost
- ~971 tokens
- SKILL.md length
- 342 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- MIT
At a glance
Regenerate the coverage report and badges, or diagnose a wrong percentage, a 404ing badge, or a package showing 0%.
- Tasks that involve Test coverage
- Calls bun
What it does
Coverage Report is an agent skill from petarzarkov/dunx. Regenerate the coverage report and badges, or diagnose a wrong percentage, a 404ing badge, or a package showing 0%. Use after adding a package, when coverage numbers look implausible, or when the published coverage site is stale or broken.
Its SKILL.md is about 970 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Test coverage. The repository describes itself as: fastest web DI framework. NestJS-style structure at Bun speed. Constructor DI with no reflect-metadata, no experimentalDecorators, no JavaScript router. The licence is MIT.
When your agent uses it
- Tasks that involve Test coverage
Example prompts
- “/coverage-report”
What it can do on your machine
Read from SKILL.md and the folder at commit 221fede. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
bun
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
dunx.win
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Coverage Report loads about 971 tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 342 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from petarzarkov/dunx at commit 221fede, republished under its MIT licence (© petarzarkov). 342 words, ~971 tokens.
Download SKILL.mdSave it as
.claude/skills/coverage-report/SKILL.md (or your agent's skills folder).- name
- coverage-report
- description
- Regenerate the coverage report and badges, or diagnose a wrong percentage, a 404ing badge, or a package showing 0%. Use after adding a package, when coverage numbers look implausible, or when the published coverage site is stale or broken.
/coverage-report
bun run test:cov # bun test --coverage from the ROOT, then gen:cov
bun run docs:build # the site is what carries the report and the badges
bun run gen:readme # only if the package set changedOrder matters. test:cov must run once from the repo root so every package
lands in a single coverage/lcov.info; running it per package overwrites that
file with one package's data.
scripts/coverage-report.ts then turns the lcov into two things, both inside
internal/docs - the site is the Pages root, coverage is a page in it:
internal/docs/src/generated/coverage.json- the model the Coverage page renders (per-package breakdown, uncovered line ranges, packages with no tests)internal/docs/public/badges/coverage.svgplus acoverage-<package>.svgeach, which the build copies verbatim to/badges/in the built site
Zero dependencies. It writes no HTML of its own any more; bun run docs:build
has to run afterwards for either output to reach the deployed site. CI does that
in the Build the documentation site step, which sits after test:cov for
exactly this reason.
Badges live in the root README's generated Packages table, in the Coverage
column added by scripts/update-readme.ts - not in per-package READMEs. A new
package picks one up automatically on the next gen:cov + gen:readme.
Lines and functions only. Bun emits no branch records, so there is no branch column to add.
Diagnosing
| Symptom | Cause |
|---|---|
| Every badge 404s on GitHub | Pages is on the default Deploy from a branch source, so GitHub serves a Jekyll render of the README. It must be set to GitHub Actions in repo settings. |
| One package's number is way off | A sibling import resolved to that sibling's dist/ and got counted alongside its src/. bunfig.toml sets coveragePathIgnorePatterns = ["**/dist/**"] - check it holds. |
Package shows grey no tests | Correct, not a bug - no test files. Grey beats a misleading 0%. |
| Numbers stale after adding tests | gen:cov ran without a fresh test:cov, so it reparsed the old lcov. |
| New package missing from the table | gen:readme not run after gen:cov. |
| Coverage page says "no coverage data" | The site was built before gen:cov ran. bun run test:cov && bun run docs:build. |
| Badges 404 but the site loads | They are at /badges/coverage-<pkg>.svg now, not the Pages root. Check scripts/update-readme.ts's DOCS_SITE. |
ci.yml publishes internal/docs/dist/ to Pages from a separate pages job on
main: https://dunx.win, with the report at
https://dunx.win/coverage.
© petarzarkov, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/coverage-report of petarzarkov/dunx.
Open the folder on GitHubat commit 221fede
Compare with similar skills
Coverage Report next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Coverage Report this skillpetarzarkov/dunx | 100 | — | ~971 | Automated safety check: Pass | MIT | |
| Requirementsrizsotto/Bear | 6.5k | — | ~2k | Automated safety check: Pass | GPL-3.0 | |
| Crap Analysisardalis/RiverBooks | 135 | 2 repos | ~3.4k | Automated safety check: Pass | None | |
| Code Coverages3s-project/s3s | 311 | — | ~789 | Automated safety check: Pass | Apache-2.0 | |
| Project Statusbactopia/bactopia | 522 | — | ~787 | Automated safety check: Pass | MIT | |
| Check Coverageldayton/Dippy | 243 | — | ~403 | Automated safety check: Pass | MIT |
Similar skills
Crap Analysis
ardalis/RiverBooks
Analyze code coverage and CRAP (Change Risk Anti-Patterns) scores to identify high-risk code.
Code Coverage
s3s-project/s3s
Measure and grow the line coverage of the s3s crate. An agent skill from s3s-project/s3s.
Project Status
bactopia/bactopia
Show a live snapshot of the Bactopia project state — component counts, GroovyDoc coverage, nf-test coverage, and structural issues.
Check Coverage
ldayton/Dippy
Ensure comprehensive test coverage for a CLI handler. An agent skill from ldayton/Dippy.
Guarding Destructive Operations
kajisho5/ffmpeg-skill
Add and review preconditions on operations that delete, overwrite, rewrite history, or resolve a caller-supplied name to a filesystem path — refusing instead of warning, placing the guard ahead of…
More from petarzarkov/dunx
Docs Pass
petarzarkov/dunx
Revise one documentation file so it states facts instead of performing insight, and get it under the budgets in scripts/no-slop.test.ts.
New Package
petarzarkov/dunx
Add a workspace to the dunx monorepo - a published package under packages/, a published CLI under tools/, a private workspace under internal/, or an example under examples/ - with correct manifest…
Release
petarzarkov/dunx
Version and publish @dunx/ packages to npm. An agent skill from petarzarkov/dunx.
Spike
petarzarkov/dunx
Resolve an open technical question by measuring it on real Bun instead of assuming, then record the verified result in docs/architecture/constraints.md.
Whats Next
petarzarkov/dunx
Write or refresh HANDOFF.md - a compact resume point holding completed objectives, live file paths, approaches already tried and rejected, and the exact next steps, placed against the roadmap in…
Related
Categories
Questions about Coverage Report
What does Coverage Report do?
Regenerate the coverage report and badges, or diagnose a wrong percentage, a 404ing badge, or a package showing 0%. Coverage Report is an agent skill from petarzarkov/dunx. Regenerate the coverage report and badges, or diagnose a wrong percentage, a 404ing badge, or a package showing 0%.
When should I use Coverage Report?
Coverage Report fits situations like: tasks that involve Test coverage.
How do I install Coverage Report in Claude Code?
Run `npx skills add petarzarkov/dunx --skill coverage-report -a claude-code`. Or copy the skill folder (.claude/skills/coverage-report in petarzarkov/dunx) into .claude/skills/coverage-report in your project. Claude Code loads it when a task matches its description.
How do I install Coverage Report in Codex?
Run `npx skills add petarzarkov/dunx --skill coverage-report -a codex`. Or copy the skill folder (.claude/skills/coverage-report in petarzarkov/dunx) into .agents/skills/coverage-report in your project. Codex loads it when a task matches its description.
Can I use Coverage Report in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add petarzarkov/dunx --skill coverage-report -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/coverage-report, .gemini/skills/coverage-report, .github/skills/coverage-report and .opencode/skills/coverage-report in your project.
What does Coverage Report need to run?
Going by SKILL.md and its folder, Coverage Report needs the command-line tools its instructions call (bun).
Does Coverage Report access the network?
SKILL.md names 1 domain. As links in the text: dunx.win. This is read from the text; nothing was executed.
Is Coverage Report safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Coverage Report use?
Coverage Report is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Coverage Report use?
About 971 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Coverage Report?
Skills that share tags, products or a category with Coverage Report: Requirements (rizsotto/Bear, 6.5k stars), Crap Analysis (ardalis/RiverBooks, 135 stars), Code Coverage (s3s-project/s3s, 311 stars) and Project Status (bactopia/bactopia, 522 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Coverage Report?
petarzarkov (a GitHub user) maintains it in petarzarkov/dunx, which has 100 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 8, 2026.
Source: petarzarkov/dunx on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.