pr-review-code

Review GitHub pull requests through local checkout and structured comment generation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/adrianschmidt/workspace-config --skill pr-review-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review-code
Source: https://github.com/adrianschmidt/workspace-config/tree/main/claude/skills/pr-review-code
Command: npx skills add https://github.com/adrianschmidt/workspace-config --skill pr-review-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured and comprehensive approach to reviewing pull requests, ensuring code quality, security, and adherence to best practices.

Core Features & Use Cases

  • Systematic Workflow: Guides through prerequisites, PR checkout, local verification, and comment generation.
  • Code Quality & Security: Focuses on logic, smells, error handling, vulnerabilities, and data handling.
  • Comment Formatting: Organizes feedback into Major Issues, Minor Issues, Nitpicks, and Positive Aspects.
  • Use Case: When asked to review a pull request, this skill will guide you through checking out the code, performing a thorough review, and formatting your feedback constructively for the user to post.

Quick Start

Use the pr-review-code skill to review pull request number 123 in the current repository.

Frequently Asked Questions about pr-review-code

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

FAQPage Schema
How do I systematically review a pull request on GitHub?

A systematic pull request review involves checking out the code locally, verifying logic, identifying security vulnerabilities and code smells, and formatting structured feedback into categorized comments.

What is the best way to format code review comments on a pull request?

The best way to format code review comments is to organize feedback into structured categories: Major Issues, Minor Issues, Nitpicks, and Positive Aspects for clear, actionable communication.

How do I check for security vulnerabilities and code smells during a PR review?

To check for security vulnerabilities and code smells during a PR review, analyze the local checkout for logic errors, poor data handling, and adherence to best practices before generating feedback.

Do I need to checkout pull request code locally to review it?

Yes, local checkout is a prerequisite step in a systematic PR review workflow to accurately verify code logic, analyze security vulnerabilities, and identify potential issues before merging.

What should a GitHub pull request review cover before merging?

A GitHub pull request review should cover code quality, security vulnerabilities, error handling, data handling, and adherence to best practices to ensure potential issues are identified before merging.