skills.rest
SkinnnyJay
SkinnnyJayCOMMUNITY
Explore all skills by this author →
𝕏@gravyskyyGitHub

coverage-report

Generates test coverage reports and identifies files below the 80% coverage threshold.

2|Updated Feb 15, 2026
Search Tags:#typescript#testing#quality assurance#npm#coverage#coverage report#test health
One-click install
npx skills add https://github.com/SkinnnyJay/simpill-utils --skill coverage-report-skinnnyjay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coverage-report
Source: https://github.com/SkinnnyJay/simpill-utils/tree/main/.claude/skills/coverage-report
Command: npx skills add https://github.com/SkinnnyJay/simpill-utils --skill coverage-report-skinnnyjay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It removes the guesswork from assessing test health by running the coverage suite, verifying artifacts, and surfacing exactly which files and code paths fall below the repository's 80% coverage requirement. ## Core Features & Use Cases - Coverage Generation: Runs npm run test:coverage and confirms artifacts are produced in .generated/coverage/. - Gap Analysis: Summarizes lines, branches, functions, and statements percentages and flags files under the 80% threshold. - Actionable Suggestions: Identifies highest-risk uncovered code paths and proposes specific tests to write. - Use Case: Before a release, run this Skill to verify the coverage gate passes and get a prioritized list of files needing more tests. ## Quick Start Run the coverage report for this repository and tell me which files are below the 80% threshold and what tests I should add.

Frequently Asked Questions about coverage-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a test coverage report for an npm project?▼

Run npm run test:coverage, which executes the test suite with coverage instrumentation and writes artifacts to .generated/coverage/. The Skill then summarizes line, branch, function, and statement percentages.

How to find files with low test coverage?▼

After generating the coverage report, compare each file's percentages against the 80% threshold. Files below that line are flagged, and the highest-risk uncovered code paths are highlighted with suggested tests.

What coverage threshold does this repository enforce?▼

The repository enforces a minimum of 80% coverage across branches, functions, lines, and statements. Any file falling below that threshold is flagged in the summary as needing additional tests.

Why does the coverage report fail to generate?▼

Generation fails when the test suite itself fails, causing npm run test:coverage to exit with a non-zero code, or when artifacts are missing from .generated/coverage/. Fix failing tests first, then rerun the coverage command.

When should I run a coverage report?▼

Run it when assessing overall test health, before cutting a release, or when deciding which files need more tests. It is not a substitute for writing tests; it only measures and reports existing coverage.

Related Skills

Explore More Software Engineering Skills→
iOfficeAIiOfficeAI
32.5k

testing

Enforces Vitest test-writing standards and coverage workflow for TypeScript projects.

Official
Intermediate
NQ-lovecppNQ-lovecpp
6

test-coverage-improver

Analyzes Python test coverage reports and proposes high-impact tests for uncovered code paths.

Community
Intermediate
jeremyaryjeremyary
7

status

Run linting, type checks, tests, and dependency audits with pass/fail reporting.

Community
Intermediate
copyleftdevcopyleftdev

lipton-mutation-testing

Inject faults into source code and calculate mutation scores for test suites.

Community
Advanced