review-coverage

Name: review-coverage
Availability: InStock
Author: doodledood

Analyze code diffs to identify and quantify test coverage gaps.

4|1|Updated Jan 11, 2026

Search Tags:#testing #diff #coverage #code-review #unit-tests #test-coverage

Ready to run

npx skills add https://github.com/doodledood/codex-workflow --skill review-coverage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-coverage
Source: https://github.com/doodledood/codex-workflow/tree/main/skills/review-coverage
Command: npx skills add https://github.com/doodledood/codex-workflow --skill review-coverage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams verify that new or modified code paths are covered by tests, reducing regressions and deployment risk.

Core Features & Use Cases

Diff-based analysis that highlights untested logic in changed files
Actionable test recommendations to close coverage gaps
Read-only reviewer workflow ideal for PRs and pre-merge checks

Quick Start

Review the diff between the current branch and origin/main to generate a focused coverage report.

Frequently Asked Questions about review-coverage

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

FAQPage Schema

How do I identify missing unit tests in my pull request diff?▼

Test coverage gap analysis works by inspecting code changes against a baseline like origin/main. It quantifies untested logic introduced by modified or added files and functions, reporting missing test cases and edge conditions while enforcing a strictly read-only review workflow.

What is the best way to check test coverage for new code paths before merging?▼

The best way to check test coverage for new code paths before merging is running a diff-based analysis on your local branch. This read-only process quantifies coverage gaps introduced by the changes and provides concrete recommendations to close them, reducing deployment risk.

Can I use diff-based test coverage analysis for local branches?▼

Yes, you can use diff-based test coverage analysis for local branches. By comparing your current branch against a baseline such as origin/main, the review process inspects modified files and functions to quantify missing tests and edge cases without making any code changes.

Does this test coverage review workflow modify my source code?▼

This test coverage review workflow does not modify your source code. It enforces a strictly read-only analysis by inspecting diffs to report missing tests, edge cases, and concrete recommendations, ensuring your repository remains untouched during the pull request review process.

When do I need to quantify test coverage gaps by inspecting diffs?▼

You need to quantify test coverage gaps by inspecting diffs when verifying that new or modified code paths are covered by tests. This process is essential during pre-merge checks and pull request reviews to reduce regressions and deployment risk introduced by code changes.