skills.rest
ramboz
rambozCOMMUNITY
Explore all skills by this author →
GitHub

pr-review

Generate a four-section markdown PR review from diffs or branch changes.

5|Updated May 12, 2026
Search Tags:#blockers#diff#scope#code-review#pr-review#nits
One-click install
npx skills add https://github.com/ramboz/jig --skill pr-review-ramboz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/ramboz/jig/tree/main/skills/pr-review
Command: npx skills add https://github.com/ramboz/jig --skill pr-review-ramboz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR reviews are often manual, repetitive, and inconsistent. This Skill generates a concise, structured four-section markdown review to standardize feedback across diffs and branches.

Core Features & Use Cases

  • Four-section review: Scope, Blockers, Nits, Strengths to summarize changes clearly.
  • Cross-language applicability: Works on PRs, diffs, or branch updates regardless of tech stack.
  • Consistent formatting: Produces a repeatable template that accelerates review cycles.

Quick Start

Invoke pr-review on a diff or branch to generate a four-section review.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I automate PR review for a branch diff?▼

Automating PR review for a branch diff involves generating a four-section markdown report covering Scope, Blockers, Nits, and Strengths to standardize feedback and accelerate review cycles.

What is the best way to structure code review feedback?▼

Structuring code review feedback is best achieved using a consistent template with Scope, Blockers, Nits, and Strengths sections, listing rationales and file paths to ensure clarity and repeatability.

Can I generate a code review report for any programming language?▼

Generating a code review report for any programming language is possible because the evaluation applies across languages and tech stacks, provided there is a PR, diff, or branch update to analyze.

How do I identify blockers and nits in a PR diff?▼

Identifying blockers and nits in a PR diff requires processing changes to list issues with specific file paths and rationales, keeping the evaluation strictly aligned with the PR's scope.

Does automated PR review keep feedback aligned with the PR scope?▼

Automated PR review keeps feedback aligned with the PR scope by summarizing changes and categorizing issues into blockers and nits with rationales, preventing scope creep during manual evaluations.

Related Skills

Explore More Software Engineering Skills→
dynatrace-ossdynatrace-oss
10

pr-reviewer

Review pull request diffs and comments to generate a structured review brief.

Official
Intermediate
NodeJSmithNodeJSmith
1

mine.address-pr-issues

Triage and resolve Pull Request blockers across GitHub and Azure DevOps.

Community
Advanced
aniruddh2003aniruddh2003
1

speckit.checker

Run static analysis tools to detect security vulnerabilities, type errors, and linting issues.

Community
Intermediate
MaxMiksaMaxMiksa
2.3k

security_audit

Audits application code, dependencies, and configurations for security vulnerabilities including OWASP Top 10 and CVEs.

Community
Advanced