review-pr

Automate GitHub pull request reviews using the gh CLI and Git worktrees.

Updated Jul 17, 2026
One-click install
npx skills add https://github.com/kolbick/Kolb-Bot --skill review-pr-kolbick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/kolbick/Kolb-Bot/tree/main/.agents/skills/review-pr
Command: npx skills add https://github.com/kolbick/Kolb-Bot --skill review-pr-kolbick

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of reviewing GitHub pull requests, providing structured feedback and assessing their readiness for merging without making any changes to the codebase.

Core Features & Use Cases

  • Comprehensive PR Analysis: Analyzes PRs for correctness, design, security, and documentation.
  • Readiness Assessment: Determines if a PR is ready for the next stage or requires further work.
  • Structured Feedback: Generates a detailed review report with actionable insights.
  • Use Case: When a new feature is submitted via a pull request, use this Skill to get a thorough, automated review before it's merged into the main branch.

Quick Start

Use the review-pr skill to analyze pull request number 123.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I automate GitHub pull request reviews?

Automating GitHub pull request reviews is achieved by using the gh CLI and Git worktrees to analyze changes, validate code quality, perform security checks, and provide structured feedback on merge readiness.

Can I check if a pull request is ready for merging automatically?

Checking if a pull request is ready for merging automatically involves analyzing the PR for existing implementations, evaluating design, and reviewing documentation to generate a detailed readiness assessment.

What does an automated code review check for in a GitHub PR?

An automated code review checks for correctness, design flaws, security vulnerabilities, and missing documentation or changelog entries within the GitHub PR to ensure comprehensive validation before integration.

How do I review a specific GitHub pull request number using automation?

Reviewing a specific GitHub pull request number using automation requires passing the PR number to the review process, which then leverages Git worktrees and the gh CLI to evaluate the changes.

Do I need the gh CLI to automate pull request analysis?

You need the gh CLI to automate pull request analysis because it provides the necessary interface to interact with GitHub, extract PR data, and perform comprehensive code and security evaluations.