Coverage Reporter

What it does

Coverage Reporter ingests your existing coverage output — from any supported format — and produces an actionable prioritised list of untested functions. It ranks gaps by a combination of function complexity, how many other functions call the untested code, and whether the file sits on a critical execution path (authentication, payments, data write operations).

After analysis, Claude can immediately generate test stubs for the top-ranked gaps so you can start filling coverage without context-switching.

• Reads lcov.info, JSON coverage reports, and plain text summaries
• Ranks untested functions by complexity and call-graph criticality
• Generates Jest, Vitest, or Pytest test stubs for uncovered functions
• Highlights files below a configurable threshold
• Works with monorepos — scoped to a package or directory

How to install

npx plugins add coverage-rep

Supported formats

• lcov — standard output from Jest, Vitest, Istanbul, nyc
• JSON — coverage-summary.json from Istanbul/nyc
• Text summary — plain stdout from pytest --cov or Jest console output

Example analysis

## Coverage Analysis — src/auth/

auth/login.ts:    43% coverage — 3 functions untested:
  • validateToken()   [HIGH priority — called by 8 routes]
  • refreshSession()  [HIGH priority — auth critical path]
  • revokeToken()     [MED  priority — admin only]

auth/register.ts: 78% coverage — 1 function untested:
  • sendVerificationEmail()  [LOW priority]

Overall auth/ coverage: 61% (threshold: 80%)

Suggested action: generate stubs for validateToken
and refreshSession — these cover the highest risk.