review-pr

Review pull requests for code quality, security, performance, and pattern adherence.

6|3|Updated Sep 13, 2017
One-click install
npx skills add https://github.com/tomholford/dotfiles --skill review-pr-tomholford
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/tomholford/dotfiles/tree/main/claude/skills/review-pr
Command: npx skills add https://github.com/tomholford/dotfiles --skill review-pr-tomholford

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This is a PR reviewer that helps teams quickly surface code quality, security, performance, and pattern-adherence issues in pull requests, reducing review time and human error.

Core Features & Use Cases

  • Automated analysis of PRs for code quality, security, and performance with actionable recommendations.
  • Consolidated view of changes, tests, and diffs to highlight risk areas and suggested improvements.
  • Use Case: when a PR is opened, run a fast, repeatable review to ensure the merged code meets project standards before approval.

Quick Start

Provide the PR number to review and generate a structured quality assessment.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I automate pull request reviews for code quality and security?

Automate pull request reviews by inspecting PR metadata, diffs, and tests to surface code quality, security, performance, and pattern adherence issues. This generates a structured assessment with actionable findings and recommendations for developer review.

Can I review GitHub PRs to check for performance and pattern adherence issues?

Yes, you can review GitHub PRs to check for performance and pattern adherence issues. The review process inspects changed files and diffs to highlight risk areas, outputting a structured quality assessment with suggested improvements.

What is the best way to surface security risks in a pull request before merging?

The best way to surface security risks in a pull request is running a fast, repeatable review that inspects PR metadata, diffs, and tests. This ensures merged code meets project standards by identifying security and quality issues before approval.

Does this automated PR review process work with Gitea workflows?

Yes, the automated PR review process works with Gitea workflows. It supports both GitHub and Gitea by inspecting PR metadata, diffs, and changed files to identify risk and quality issues for developer review.

How do I start a code quality assessment using a PR number?

To start a code quality assessment, provide the PR number to the reviewer. It will inspect the pull request changes, tests, and diffs to generate a structured assessment with findings, recommendations, and a summary.

What limitations should I expect when automating code review for pull requests?

When automating code review for pull requests, expect the output to be a structured assessment designed to support developer review rather than replace it entirely. The analysis surfaces risk areas and quality issues but still requires human judgment for final approval.