pr-review

Name: pr-review
Availability: InStock
Author: PodCodar

Review GitHub pull requests for correctness, security, and maintainability issues.

7|1|Updated Jul 27, 2021

Search Tags:#diff analysis #code review #best practices #pull request #security #github #engineering feedback

Ready to run

npx skills add https://github.com/podcodar/webapp --skill pr-review-podcodar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/podcodar/webapp/tree/main/.agents/skills/pr-review
Command: npx skills add https://github.com/podcodar/webapp --skill pr-review-podcodar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams catch issues in pull requests early by providing a structured review focused on correctness, security, maintainability, and performance.

Core Features & Use Cases

Systematic PR review: Evaluates each changed file in context to produce actionable feedback.
Security and best-practice checks: Flags injection risks, secret exposure, and missing authorization/authentication patterns.
Clear, severity-based responses: Labels findings as [blocker], [warning], or [suggestion] and recommends next steps with rationale.
Use Cases: Reviewing code changes in src/ and tests, validating documentation updates, and handling large PRs by triaging with diff stats.

Quick Start

Ask the AI to review the specified GitHub pull request URL and return a prioritized set of findings with severity labels and next-step recommendations.

Frequently Asked Questions about pr-review

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

FAQPage Schema

How do I review a GitHub pull request for security and maintainability issues?▼

To review a GitHub pull request, fetch the diff using the authenticated `gh` CLI, then evaluate changed files for correctness, security, and performance. The output is structured feedback with severity labels like [blocker] or [warning] and actionable next-step recommendations.

What is the best way to triage large pull requests with many file changes?▼

The best way to triage large pull requests is using diff stats to perform file-by-file evaluation across src, tests, and documentation. This method isolates critical security and correctness issues, returning a structured response with severity labels for actionable engineering feedback.

Do I need an authenticated GitHub CLI session to analyze a pull request diff?▼

Yes, you need an authenticated GitHub `gh` CLI session to analyze a pull request diff. The review process uses `gh pr view` and `gh pr diff` commands or URL-based diff fetching to securely retrieve changes and output prioritized feedback with severity labels.

Can I get automated code review feedback for my src and test files before merging?▼

Yes, you can get automated code review feedback for src and test files before merging. The review evaluates each changed file in context, labeling findings as [blocker], [warning], or [suggestion] to validate documentation updates and catch missing test coverage or security flaws.

How does automated pull request review handle secret exposure and injection risks?▼

Automated pull request review handles secret exposure and injection risks by performing security and best-practice checks across the diff. It flags these vulnerabilities with clear severity labels and recommends next steps with rationale to prevent insecure code from merging.