pr-review

Automate GitHub pull request reviews with inline comments and structured JSON payloads.

1|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/bossjones/boss-skills --skill pr-review-bossjones
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/bossjones/boss-skills/tree/main/plugins/boss-dev/agent-harness/skills/pr-review
Command: npx skills add https://github.com/bossjones/boss-skills --skill pr-review-bossjones

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The pr-review Skill solves the problem of manually reviewing GitHub pull requests, providing an automated approach to code review with schema-validated review payloads.

Core Features & Use Cases

  • Automated Pull Request Review: Automates the process of reviewing GitHub pull requests, including inline comments and an approve-or-comment decision.
  • Schema-Validated Payloads: Ensures that the review comments and decisions follow a structured format.
  • Use Case: Ideal for developers who need to review multiple pull requests or want to streamline their code review process with structured feedback.

Quick Start

Use the pr-review skill to review a GitHub pull request with the command: /pr-review <owner_repo> <pr_number> [extra_context].

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I automate GitHub pull request code reviews?

Automated GitHub pull request code reviews are handled by analyzing code changes, generating inline comments, and outputting a schema-validated review payload with an approve-or-comment decision.

What is JSON schema validation for pull request review payloads?

JSON schema validation for pull request review payloads ensures that automated review comments and approve-or-comment decisions strictly follow a structured, predefined format.

Do I need GitHub API access to run an automated pull request review?

GitHub API access is required to run automated pull request reviews, as the analysis fetches code changes and posts inline comments directly to the GitHub platform.

What's the best way to provide extra context when reviewing a GitHub pull request?

Providing extra context when reviewing a GitHub pull request is done by appending it to the command, allowing the automated analysis to incorporate specific instructions alongside code changes.

Can I use automated code review for multiple GitHub pull requests?

Automated code review is ideal for developers needing to review multiple GitHub pull requests, streamlining the process by generating structured feedback and inline comments consistently.

How does automated code review handle inline comments on GitHub?

Automated code review handles inline comments by analyzing specific code changes within the pull request and generating targeted, schema-validated feedback directly on the GitHub diff.