analyze-pr

Generate context-aware PR quality checklists from changed files and diffs.

3|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/kapilvirenahuja/garura --skill analyze-pr-kapilvirenahuja
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-pr
Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/skills/analyze-pr
Command: npx skills add https://github.com/kapilvirenahuja/garura --skill analyze-pr-kapilvirenahuja

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It eliminates uncertainty in pull request readiness by producing a context-aware quality checklist based on what changed.

Core Features & Use Cases

  • Branch-diff analysis: Compares the current branch against a base branch (default main) and selects relevant checks from the changed files and commit history.
  • PR-scoped analysis: When a pr_number is provided, fetches diff and PR metadata via the platform-adapter to analyze exactly what the PR changes.
  • Deterministic, evidence-first checklist: Loads quality rules, applies branch-pattern overrides (hotfix/release/experiment), runs automated verifications where applicable, and marks manual items as REVIEW.

Quick Start

Ask your agent to analyze the current branch against main and return a context-aware PR quality checklist with blocking issues and evidence.

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 context-aware quality checklist for a pull request?

To generate a context-aware quality checklist for a pull request, analyze changed files and commit history against a base branch to produce deterministic, evidence-oriented readiness checks before merging.

How does branch-diff analysis work for PR readiness assessment?

Branch-diff analysis for PR readiness assessment works by comparing the current branch against a base branch like main, loading quality rule sets, and applying priority overrides based on branch naming patterns like hotfix or release.

Can I analyze a specific pull request by its number instead of a branch diff?

Yes, you can analyze a specific pull request by providing a PR number, which fetches diff and PR metadata via a platform-adapter to evaluate exactly what the PR changes.

What is the best way to apply branch-pattern overrides for release readiness checks?

The best way to apply branch-pattern overrides for release readiness checks is by matching branch naming patterns against defined rules, automatically prioritizing specific quality verifications for hotfix, release, or experiment branches.

Does PR analysis support security scanning and CI verification before merging?

PR analysis supports security scanning and CI verification by running automated checks where applicable within the generated checklist and explicitly marking manual verification items as REVIEW.

What are the limitations of using git diff for PR quality analysis?

A limitation of using git diff for PR quality analysis is that branch-diff mode only compares changes against a base branch, requiring a PR number and platform-adapter to fetch full PR metadata for scoped analysis.