analyze-pr

Analyze GitHub pull requests and generate manual QA test plans.

7|1|Updated Jun 24, 2025
One-click install
npx skills add https://github.com/schutera/highfive --skill analyze-pr-schutera
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-pr
Source: https://github.com/schutera/highfive/tree/main/.claude/skills/analyze-pr
Command: npx skills add https://github.com/schutera/highfive --skill analyze-pr-schutera

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the uncertainty of whether a GitHub PR is fully validated by automation, by turning CI-and-local-test coverage into a precise checklist of remaining manual tasks.

Core Features & Use Cases

  • PR targeting and resolution: Accepts a PR number, the current branch, or auto-selects when exactly one open PR exists, then gathers PR metadata and status checks.
  • Deep test-layer execution: Runs all locally runnable validation layers across docs-citation gates, backend, frontend, database, image analysis, ESP32-CAM native tests, and optionally UI tests when appropriate.
  • Manual QA plan generation: Produces a short, falsifiable, copy-paste-ready manual test plan by combining PR body checkboxes, linked issue acceptance criteria, and risk-surface checks implied by the diff.

Quick Start

Run the analyze-pr skill with the pull request number, for example analyze-pr 125, to generate a concise manual-test plan for whatever is left after automated checks.

Frequently Asked Questions about analyze-pr

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

FAQPage Schema
How do I generate a manual QA checklist for a GitHub pull request?

A manual QA checklist for a GitHub pull request is generated by fetching PR metadata and linked issues, running local test layers, and outputting a falsifiable, copy-paste-ready manual test plan covering remaining unverified tasks.

What is risk-based validation for pull requests?

Risk-based validation for pull requests is the process of combining CI status checks, local test execution, and diff-informed risk-surface checks to identify what manual quality assurance work remains unverified before merging.

How do I run local test automation before manual QA on a PR?

You run local test automation before manual QA by executing all locally runnable validation layers across backend, frontend, database, docs-citation gates, and native tests, then outputting the remaining manual test plan.

Can I auto-select a pull request if only one is open?

Yes, a pull request can be auto-selected when exactly a single open PR exists in the repository, which then gathers PR metadata and status checks to build the manual test plan.

Does the manual test plan include acceptance criteria from linked issues?

Yes, the manual test plan includes acceptance criteria from linked issues, combining them with PR body checkboxes and diff-informed risk-surface checks to produce a concise falsifiable checklist.

What are the limitations of relying on local test execution for PR validation?

Local test execution limitations include only covering locally runnable validation layers like backend, frontend, and database tests, leaving diff-informed risk-surface checks and manual QA tasks for unverified areas.