review-pr

Review GitHub and GitLab PR/MR diffs for regressions, risks, and missing tests.

2|Updated Dec 8, 2018

Search Tags:#automation #checklist #review #diff #code-review #pull-request

One-click install

npx skills add https://github.com/indykish/dotfiles --skill review-pr-indykish

Or copy as Structured Prompt for Agent▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review a pull request or merge request by analyzing only the changed code to surface regressions, risks, and missing tests.

Core Features & Use Cases

Detect forge and determine the proper CLI workflow.
Fetch the PR/MR diff and metadata from GitHub or GitLab.
Review the changed code against a comprehensive, structured checklist covering security, correctness, performance, tests, API design, code quality, and language-specific guidelines.
Output findings in a consistent, human- and machine-readable format for easy decision-making.
Use cases: before approving or merging PRs, during teammate changes reviews, or after CI completes but before final sign-off.

Quick Start

Provide the PR URL and run the review command to analyze the changed code.

Frequently Asked Questions about review-pr

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

FAQPage Schema

How do I review a pull request for regressions and missing tests?▼

You can review a pull request by providing the PR or MR URL to an automated forge-aware CLI workflow that fetches diffs, retrieves metadata, and checks changed code against a structured checklist covering security, correctness, performance, and missing tests.

Can I use this to review GitLab merge requests as well as GitHub pull requests?▼

Yes, you can review GitLab merge requests and GitHub pull requests. The tool automatically detects the forge to determine the proper CLI workflow for fetching and analyzing the MR or PR diff and metadata.

What does an automated code review checklist cover for changed diff code?▼

An automated code review checklist for changed diff code covers security, correctness, performance, tests, API design, code quality, and language-specific guidelines to surface regressions and risks before merging.

When should I run an automated PR review during the CI pipeline?▼

You should run an automated PR review after CI completes but before final sign-off, or during pre-merge approvals and teammate change reviews, to surface risks and missing tests in the changed code.

What is the best way to analyze a PR diff for security and performance risks?▼

The best way to analyze a PR diff for security and performance risks is using an automated tool that fetches metadata and runs the changed lines against a comprehensive, structured checklist to output a formatted findings report for decision-making.

Does the code review output a machine-readable findings report?▼

Yes, the code review outputs findings in a consistent format that is both human- and machine-readable, allowing for easy integration into automated decision-making processes before final sign-off.