pr-review

Reviews GitLab merge requests and GitHub pull requests, posting inline comments and verdicts.

Updated Apr 12, 2026

Search Tags:#code review #pull request #github #jira #gitlab #merge request #inline comments

One-click install

npx skills add https://github.com/azborgonovo/ai-skills --skill pr-review-azborgonovo

Or copy as Structured Prompt for Agent▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Reviewing a merge request or pull request by hand means fetching the change, finding its linked work item, checking out the right commit, writing findings, and then manually posting each comment and verdict on the host. This Skill automates that entire loop so the review lands on the change itself as inline comments plus an approval or request-changes verdict. ## Core Features & Use Cases - End-to-end review publishing: Fetches change metadata and the linked Jira or GitHub work item, isolates the change in a disposable git worktree, delegates the diff review to the review-changes skill, then posts every finding as an inline comment anchored to the diff. - Host and tracker adapters: Ships adapters for GitLab and GitHub as code hosts and Jira and GitHub Issues as trackers, with graceful degradation to tool discovery for other platforms. - Three review modes: Default mode publishes comments and records the verdict, comments-only publishes without touching approval state, and draft mode leaves a pending review for the user to submit. Self-authored changes automatically drop to comments-only. - Use Case: Run /pr-review on a GitLab MR URL and the author receives inline comments with one-click suggestion blocks, a request-changes summary when blocking findings exist, and you receive a full review report in the conversation. ## Quick Start Ask the AI to run /pr-review followed by the URL of a GitLab merge request or GitHub pull request you want reviewed.

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 with inline comments automatically?▼

Invoke /pr-review with the pull request URL. The skill fetches the PR metadata and linked work item, checks out the head SHA in a disposable worktree, runs the review, and posts each finding as an inline comment using the gh CLI, then records an approval or request-changes verdict.

How do I review a GitLab merge request against its Jira ticket?▼

Pass the merge request URL to /pr-review. The skill scans the MR title and description for a Jira key, fetches the issue summary and acceptance criteria via the twg CLI or Atlassian MCP tools, and hands that spec to the review so findings are checked against the actual requirements.

Can I post review comments without approving or requesting changes?▼

Yes. Run /pr-review with the comments-only mode to publish findings without touching the approval state, or use draft mode to leave a pending review you submit manually. Self-authored changes automatically fall back to comments-only because both hosts reject self-approval.

Does the skill work with code hosts other than GitLab and GitHub?▼

It ships dedicated adapters for GitLab and GitHub only. For other hosts it degrades by discovering available tools through ToolSearch and runs in comments-only mode, since recording a verdict through an unverified interface is not attempted.

What happens if the review is rerun on the same merge request?▼

The posting scripts mark every comment with a robot emoji and skip any finding that this account already published, matching on the same file and line or identical text. Published comments are never deleted or overwritten, so author replies stay intact.

Why does the skill use a git worktree instead of checking out the branch?▼

A disposable worktree detached at the change's head SHA avoids switching the branch or disturbing uncommitted work in your main clone. If no worktree can be created, the review falls back to a diff-only mode and reports that limitation as a caveat.