review-pr

Generate evidence-based review findings for GitHub Pull Requests or GitLab Merge Requests.

9|2|Updated Apr 6, 2026

Search Tags:#code quality #diff analysis #security #merge request #inline comments #pull request review #GitHub GitLab

One-click install

npx skills add https://github.com/Dawn-Technology/aicelerate --skill review-pr-dawn-technology

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/Dawn-Technology/aicelerate/tree/main/plugins/aimate/skills/review-pr
Command: npx skills add https://github.com/Dawn-Technology/aicelerate --skill review-pr-dawn-technology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you review GitHub Pull Requests or GitLab Merge Requests by producing constructive, evidence-based findings and proposing code fixes without directly modifying the repository.

Core Features & Use Cases

Provider-aware PR/MR analysis: Detects whether the request targets GitHub or GitLab and uses the matching tooling for diffs, discussions, and review artifacts.
Full diff-driven review with codebase context: Fetches and checks out an isolated worktree, gathers conventions via a subagent, retrieves diffs, and traces control-flow impact across files.
Structured findings with severity: Classifies issues across security, correctness, maintainability, and scope consistency, then presents results for user confirmation.
Actionable outputs with workflow actions: After approval, can post inline structured comments, approve, or request changes (including reviewer assignment on GitLab).

Quick Start

Ask the agent to review the pull request: "Review this GitHub PR: <PR_URL> and list the security, correctness, and maintainability issues with suggested fixes."

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 GitHub pull request for security and correctness issues?▼

Automated pull request review detects the GitHub provider, retrieves the diff, and analyzes codebase context via an isolated worktree. It classifies security and correctness issues by severity, providing actionable suggestions anchored to specific diff locations.

Can I post inline comments directly to a GitLab merge request?▼

Yes, you can post inline comments to a GitLab merge request. After generating categorized findings and receiving user approval, the tool posts structured comments, approves the MR, or submits change requests with reviewer assignment directly on the platform.

Does automated PR review work with both GitHub and GitLab?▼

Automated PR review works with both GitHub and GitLab through provider-aware analysis. The system automatically detects the target platform and applies the matching tooling for diff retrieval, discussion threading, and review artifact generation.

How does pull request diff analysis handle existing review threads?▼

Pull request diff analysis handles existing review threads using prior-thread de-duplication. The system checks out an isolated git worktree, gathers repository conventions, retrieves diffs, and traces control-flow impact across files while avoiding duplicate review comments.

What is the best way to categorize code quality findings in a merge request?▼

The best way to categorize code quality findings in a merge request is by severity and type. The system classifies issues across security violations, requests for change, and optional suggestions, anchoring actionable fixes to specific diff locations for user confirmation.

Do I need a git worktree to analyze pull request diffs?▼

Yes, a git worktree is required to analyze pull request diffs. The tool uses git worktree isolation to safely check out the code, gather conventions via a subagent, and trace control-flow impact across files without modifying the main repository.