agent-pr-test-analyzer

Reviews pull request test coverage for behavioral completeness and real bug prevention.

5|15|Updated Jul 8, 2026
One-click install
npx skills add https://github.com/clfigueiredo/hermes-infra-skills --skill agent-pr-test-analyzer-clfigueiredo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-pr-test-analyzer
Source: https://github.com/clfigueiredo/hermes-infra-skills/tree/main/.hermes/skills/curso-hermes/agent-pr-test-analyzer
Command: npx skills add https://github.com/clfigueiredo/hermes-infra-skills --skill agent-pr-test-analyzer-clfigueiredo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pull requests often ship with tests that miss the actual changed behavior, leaving critical code paths untested and bugs undetected. This Skill reviews whether a PR's tests genuinely cover the modified code, flagging coverage gaps before they reach production. ## Core Features & Use Cases - Changed Code Mapping: Identifies modified functions, classes, and modules, then locates their corresponding tests to expose untested code paths. - Behavioral Coverage Analysis: Verifies that features, edge cases, error paths, and important integrations are actually tested. - Test Quality Review: Flags weak assertions, flaky patterns, and poor test isolation, rating gaps as critical, important, or nice-to-have. - Use Case: Before merging a pull request that refactors a payment module, run this Skill to confirm the new logic has meaningful assertions and that error-handling branches are covered. ## Quick Start Invoke the skill with /skill agent-pr-test-analyzer followed by the pull request diff or description of the changed code you want reviewed.

Frequently Asked Questions about agent-pr-test-analyzer

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

FAQPage Schema
How do I check if my pull request has enough test coverage?▼

Run the pr-test-analyzer review on your PR diff. It maps changed functions and modules to their tests, identifies untested code paths, and rates coverage gaps as critical, important, or nice-to-have so you know what to fix before merging.

What does behavioral test coverage mean in code review?▼

Behavioral coverage means tests verify the actual changed behavior, not just that code runs without throwing. The analyzer checks that each feature has tests, edge cases and error paths are covered, and important integrations are exercised.

How do I detect weak or flaky tests in a pull request?▼

The analyzer flags no-throw assertions that lack meaningful checks, flaky test patterns, and poor isolation or unclear test names. It prefers meaningful assertions and reports these as test quality findings in its review output.

Can this review untested code paths in a large diff?▼

Yes. It maps changed functions, classes, and modules first, then locates corresponding tests to identify new untested code paths. Gaps are rated by impact so large diffs can be triaged starting with critical items.

What are the limitations of automated PR test review?▼

The review relies on evidence from the provided diff and test files; it does not execute tests or fabricate results. It cannot judge runtime behavior, so findings should be confirmed with actual test runs in CI.