pr-review

Review pull requests for correctness, security, performance, and maintainability.

Updated Feb 18, 2026

Search Tags:#performance #security #maintainability #code-review #diffs #pull-request #pr-review

Ready to run

npx skills add https://github.com/askaret/codex-skills --skill pr-review-askaret

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps reviewers catch defects before merging by evaluating PRs for correctness, security, performance, and maintainability, and by generating actionable diffs or TODOs.

Core Features & Use Cases

API compatibility & error handling
AuthN/AuthZ assumptions
Input validation & logging (no secrets)
Tests added/updated and what’s missing
Frontend performance/regressions (renders, memoization, data fetching)
DX: docs, scripts, onboarding

Quick Start

Review the latest pull request by providing its diff and relevant context to generate actionable diffs and a TODO list.

Frequently Asked Questions about pr-review

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

FAQPage Schema

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

Automate a pull request review by providing the PR diff and relevant context to evaluate correctness, security, performance, and maintainability, generating actionable diffs or a TODO list.

What should a code review check for in authentication and API changes?▼

A code review for authentication and API changes should verify API compatibility, error handling, AuthN/AuthZ assumptions, input validation, and logging to ensure no secrets are exposed.

Can I check frontend regressions like memoization and data fetching in a PR diff?▼

Yes, evaluating frontend regressions in a PR diff covers renders, memoization, and data fetching to identify performance issues and maintainability concerns before merging.

How do I ensure test coverage is evaluated across backend and frontend changes?▼

Ensure test coverage by reviewing the PR diff to identify which tests were added or updated, and generating a TODO list detailing what specific test coverage is still missing.

Does the pull request review process check developer experience and onboarding docs?▼

Yes, the pull request review process evaluates developer experience by checking documentation, scripts, and onboarding materials to ensure maintainability and clear team workflows.