test-coverage

Detect test coverage gaps introduced by code changes and output recommendations.

2|Updated Sep 13, 2025
One-click install
npx skills add https://github.com/s977043/river-reviewer --skill test-coverage-s977043
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-coverage
Source: https://github.com/s977043/river-reviewer/tree/main/skills/agent-skills/test-coverage
Command: npx skills add https://github.com/s977043/river-reviewer --skill test-coverage-s977043

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Detects missing tests and coverage gaps introduced by changes to guide test planning.

Core Features & Use Cases

  • Coverage checks: spot new branches and edge cases that lack tests.
  • Regression guard: ensure existing behavior remains protected.
  • Quick Start: pass a patch and receive coverage-gap notes.

Quick Start

Run on a patch/diff to surface missing tests and recommended coverage improvements.

Frequently Asked Questions about test-coverage

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

FAQPage Schema
How do I identify test coverage gaps when code changes?

Test coverage gap detection analyzes diffs against your test suite to surface untested branches and edge cases introduced by code changes. Apply it to new features, expanded logic, and bug fixes to spot missing unit, integration, and end-to-end tests before deployment.

Can I use coverage analysis on patches to guide test planning?

Yes. Pass a patch or diff to surface coverage gaps and receive actionable recommendations for minimal test strategies. This helps prioritize which new code paths require test coverage.

What types of code changes does coverage detection cover?

Coverage detection applies to new feature additions, expanded logic branches, and bug fixes. It analyzes behavioral changes across unit, integration, and end-to-end test levels to identify gaps.

How does coverage analysis protect against regressions?

Coverage detection ensures existing behavior remains protected by flagging when changes introduce new untested branches. This guards against regressions by confirming test coverage extends to modified code paths.

What inputs does test coverage analysis require?

Coverage analysis requires access to repository files, test directories, and code diffs. It examines these inputs to detect behavioral changes and output test-coverage recommendations.

When should I run coverage gap detection in my development workflow?

Run coverage analysis after making code changes—during code review, before merging patches, or when adding features—to ensure new logic has corresponding test coverage before deployment.