review-coverage

Identify untested new and modified Go code using built-in coverage tooling.

9|Updated Mar 22, 2026

Search Tags:#code review #pull request #go #software quality #test coverage #go tests #coverage gaps

Ready to run

npx skills add https://github.com/paultyng/skill-issue --skill review-coverage-paultyng

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of untested new and modified Go code going undetected before merge, which can lead to regressions and bugs in production that the existing test suite does not catch.

Core Features & Use Cases

Scoped Coverage Analysis: Run test coverage against full codebases, specific packages, or only changed files from a PR or branch diff to focus on relevant code.
Severity-Graded Findings: Automatically grade uncovered functions by risk (high for security/error-handling code, medium for business logic, low for trivial helpers) to prioritize fixes.
Coverage Delta Tracking: Compare current coverage against prior review baselines to spot regressions in test coverage over time. Use Case: For a Go team reviewing a PR that adds new payment processing functions, use this skill to quickly identify which of those new functions have no test coverage, so you can request tests before merging.

Quick Start

Ask the review-coverage skill to analyze test coverage gaps for the new and modified Go code in your current pull request.

Frequently Asked Questions about review-coverage

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

FAQPage Schema

How do I check Go test coverage for changed files in a pull request?▼

You can identify untested Go code in a pull request by running scoped test coverage analysis against the branch diff. This generates per-package reports and severity-graded findings for uncovered functions to prevent regressions before merging.

What is the best way to find untested Go functions during code review?▼

The best way to find untested Go functions during code review is to generate severity-graded coverage findings. This highlights uncovered security and error-handling code as high risk, helping prioritize which missing tests to request before merging.

Can I track Go test coverage deltas against a prior baseline?▼

Yes, you can track Go test coverage deltas against prior review baselines. Comparing current coverage against previous baselines spots test coverage regressions over time, ensuring new code changes maintain software quality.

Does this Go test coverage analysis work on specific packages or full repositories?▼

Yes, Go test coverage analysis supports scoped analysis of specific packages, changed files from a branch diff, or entire repositories. This flexibility helps focus code review on relevant new and modified code.

How are uncovered Go functions graded by risk during coverage gap analysis?▼

During coverage gap analysis, uncovered Go functions are graded by severity: high for security and error-handling code, medium for business logic, and low for trivial helpers. This severity grading prioritizes fixes for the highest risk code.

Why do I need to analyze test coverage gaps for modified Go code?▼

Analyzing test coverage gaps for modified Go code is needed because untested changes going undetected before merge lead to production regressions. Identifying these gaps ensures the existing test suite catches new code paths.