pr-test-analyzer

Analyze pull requests to evaluate test coverage quality and completeness.

18|2|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/jaredpalmer/agentik --skill pr-test-analyzer-jaredpalmer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-test-analyzer
Source: https://github.com/jaredpalmer/agentik/tree/main/.agents/skills/pr-test-analyzer
Command: npx skills add https://github.com/jaredpalmer/agentik --skill pr-test-analyzer-jaredpalmer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps engineers and reviewers ensure PRs include sufficient tests by evaluating coverage quality and identifying critical gaps that may cause regressions.

Core Features & Use Cases

  • Behavioral coverage evaluation across changed code paths
  • Edge-case and negative-test identification for critical logic
  • Actionable recommendations with suggested test cases and scenarios

Quick Start

Review the PR and its tests, and generate a targeted test-coverage review with recommended test cases.

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 PR test coverage for edge cases during code review?

To check PR test coverage for edge cases during code review, analyze the pull request to evaluate behavioral coverage across changed code paths and identify critical gaps in negative tests to prevent regressions.

What is behavioral testing coverage evaluation in a pull request?

Behavioral testing coverage evaluation in a pull request is the process of verifying that critical logic paths and changed code are sufficiently tested, ensuring project quality standards are met before merging.

How do I find missing negative tests and edge cases in my changed code paths?

To find missing negative tests and edge cases in changed code paths, analyze the PR to identify gaps in critical logic and receive actionable recommendations with suggested test cases and scenarios.

Can I get actionable test case recommendations for untested logic before merging?

Yes, you can get actionable test case recommendations for untested logic before merging by assessing the PR to identify coverage gaps and generate a targeted test-coverage review with structured test scenarios.

When do I need to analyze test coverage quality for feature changes?

You need to analyze test coverage quality for feature changes when you want to ensure critical logic paths are tested, identify edge-case gaps, and prevent regressions before merging code into the main branch.