Engineering / Testing Quality

Coverage Gap Reporter

Parse coverage outputs, map changed files to uncovered risk areas, and recommend targeted tests.

DocumentationAgent instructionsRequirements & limits

Use when coverage artifacts need to be mapped to changed files and uncovered regression risk.

Inputs

  • coverage report or JSON artifact
  • changed files or target module list
  • coverage adapter or report format hint

Outputs

  • Coverage gap report
  • Risk-ranked files
  • Suggested tests

Before you begin

  • Reading and copying the procedure require no terminal setup. Check requirements for any packaged programs separately.

Try this first

Read the procedure and supply its documented inputs. Use the full text in an agent app or chat that supports pasted instructions, following that host's guidance.

Limits for this step
  • Instruction package only; it does not provide or authorize an executable runtime capability.
  • Safe for coverage analysis and recommendation; require human approval before modifying CI coverage gates.
Read full instructionsHide full instructionsSKILL.md · v0.1.0

Coverage Gap Reporter

When to use

  • Use when a PR or branch has fresh coverage output.
  • Use when you need coverage evidence for changed files.
  • Use when coverage dropped and the next test target is unclear.

Inputs required

  • coverage report or JSON artifact
  • changed files or target module list
  • coverage adapter or report format hint

Workflow

  1. Parse the coverage source using the configured adapter.
  2. Isolate changed files or requested modules.
  3. Report per-file coverage and notable uncovered areas.
  4. Translate uncovered areas into concrete test suggestions.
  5. Call out missing or incompatible coverage data explicitly.

Output format

  • Coverage Summary
  • Changed File Coverage
  • Uncovered Risk Areas
  • Suggested Tests
  • Data Quality Notes

Guardrails

  • Do not guess line coverage when the report is incomplete.
  • Distinguish missing coverage data from low coverage.
  • Tie recommendations to reported uncovered areas.
  • Keep outputs deterministic and file-scoped.

Failure modes

  • If no adapter matches the report, ask for the supported format.
  • If changed files are absent from the report, mark the result incomplete.
  • If coverage is stale, say so explicitly.
View file metadata
---
name: coverage-gap-reporter
description: Interpret coverage reports for changed code and turn them into
  actionable, file-level test recommendations.
---

Summary sources · Catalogue metadata, skill.yaml, SKILL.md, examples/input.json, examples/output.json · v0.1.0 · Release package

Install instruction files

These commands copy guidance into the selected runtime directories. Confirm that your agent app discovers it. Any packaged programs need separate setup and verification.

Install (Codex)

./bin/skills-hub install engineering/[email protected] --runtime codex

Install (Claude)

./bin/skills-hub install engineering/[email protected] --runtime claude

Install (Generic)

./bin/skills-hub install engineering/[email protected] --runtime generic --target ./my-agent/skills

How You Can Use This

Documentation

Resource form: Agent instructions

Read or copy the guidance. Any packaged programs have separate execution requirements and evidence.

First run: Read SKILL.md and follow the documented workflow.

Current limits

  • Instruction package only; it does not provide or authorize an executable runtime capability.
What installation and verification mean
File installation
Places package files and generated configuration in the selected directories.
Native discovery
Your agent app finds and accepts the instructions, tools or plugin registrations.
Mock execution
Exercises sample fixtures. Connected data and provider effects need a separate check.
Connected operation
Requires current configuration, provider authentication, scoped permissions and a successful operation in your intended environment.

Declared compatibility

Compatibility unknown: versions and capabilities have not been declared.

Classification: declared

Technical details and release files

Operational Summary

Execution mode: analysis-only

Approval boundary: Safe for coverage analysis and recommendation; require human approval before modifying CI coverage gates.

Review and lifecycle

Review maturity: Experimental

Security review declaration: Not declared

Lifecycle: Active

These release declarations are separate from evidence that a workflow operates in your environment.

Runtime & Dependencies

ID: engineering/coverage-gap-reporter

Tags: coverage, tests, reporting, quality

Runtimes: codex, claude, generic

Tool dependencies: 0

API dependencies: 0

Dependencies

Tools: Not documented

APIs: Not documented

Outputs

  • Coverage gap report
  • Risk-ranked files
  • Suggested tests