pr-test-analyzer

Identify test coverage gaps in pull requests before review.

1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/bcmcpher/my-skills --skill pr-test-analyzer-bcmcpher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-test-analyzer
Source: https://github.com/bcmcpher/my-skills/tree/main/plugins/programming-tools/agents/pr-test-analyzer
Command: npx skills add https://github.com/bcmcpher/my-skills --skill pr-test-analyzer-bcmcpher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze test coverage quality and completeness for a pull request or set of changes. Delegate to this agent when the user asks "are the tests thorough?", "check my test coverage", "review the tests in this PR", or "are there gaps in my tests?" — especially before marking a PR ready for review. Focuses on behavioral coverage and critical gaps, not line-coverage metrics.

Core Features & Use Cases

  • Assess whether the PR exercises critical paths and behavioral scenarios.
  • Identify missing test cases and edge conditions that could cause regressions.
  • Provide actionable recommendations to improve test suites and surface gaps before PR approval.

Quick Start

Use pr-test-analyzer to evaluate the current PR's tests and surface gaps for quick remediation.

Frequently Asked Questions about pr-test-analyzer

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

FAQPage Schema
How do I check my PR test coverage for behavioral gaps before review?

PR test coverage gap analysis evaluates whether your pull request tests exercise critical paths, edge cases, and integration points. It focuses on behavioral coverage assessment rather than line-coverage metrics to surface missing scenarios before approval.

What is behavioral test coverage and how does it differ from line coverage?

Behavioral test coverage assesses whether tests exercise critical code paths and expected scenarios, not just executed lines. It identifies missing edge cases and negative conditions that could cause regressions, providing actionable recommendations for test suite improvements.

How do I identify missing edge cases and negative test scenarios in my code changes?

To identify missing edge cases, analyze test coverage across changed code paths and integration points. Assess behavioral coverage for negative cases and critical paths to find gaps that could cause regressions, then apply actionable recommendations to remediate them.

Can I use this to review tests in a pull request before marking it ready?

Yes, you can review tests in a pull request before marking it ready by applying behavioral coverage assessment. It evaluates changed code paths, edge conditions, and integration points to surface gaps and provide actionable recommendations for quick remediation.

What's the best way to find untested critical paths in a pull request?

The best way to find untested critical paths is performing a structured PR review focused on behavioral coverage assessment. Evaluate changed code paths, negative cases, and integration points to identify deficiencies and generate actionable recommendations to improve test suites.

Are there limitations to behavioral coverage analysis for integration points?

Behavioral coverage analysis for integration points depends on the visibility of changed code paths within the PR. It focuses on surfacing gaps in critical paths and negative cases but does not calculate quantitative line-coverage metrics for external dependencies.