review-pr

Reviews GitHub pull requests, fixes safe issues, and reports merge readiness.

7|5|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/nebius/nebius-ps-services --skill review-pr-nebius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/review-pr
Command: npx skills add https://github.com/nebius/nebius-ps-services --skill review-pr-nebius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Reviewing pull requests manually means juggling diffs, CI checks, reviewer comments, merge conflicts, and branch permissions across multiple tools, and it is easy to miss blockers or accidentally rewrite someone else's branch. This Skill automates the full PR review workflow so a pull request moves closer to merge-ready state safely. ## Core Features & Use Cases - Comprehensive PR Inspection: Resolves a PR by number, URL, or current branch, then inspects the diff, checks, review decision, conflicts, and unresolved reviewer concerns against the base branch. - Safe Automated Fixes: Applies safe code, test, workflow, or documentation fixes directly on writable branches, resolves straightforward conflicts, and runs focused validation such as ruff, pytest, shellcheck, actionlint, or helm lint. - Agentic SDLC Review Mode: For PRs tied to an active Agentic SDLC run, switches to findings-and-readiness-only mode that never mutates the promoted PR head and routes required changes back through the SDLC coordinator. - Use Case: A teammate asks you to check whether PR #142 is ready to merge. The Skill fetches the PR state, finds a failing shell check, fixes the script on the writable branch, reruns shellcheck, and reports the PR as ready with no remaining blockers. ## Quick Start Ask the agent to review pull request number 142 against its base branch and report whether it is ready to merge.

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 from the command line?

Use the GitHub CLI with gh pr view and gh pr diff to inspect metadata and changed files, then gh pr checkout to test the branch locally. This Skill automates that flow, checking CI status, review decisions, and conflicts before reporting merge readiness.

How to fix issues directly on a pull request branch?

When the branch is writable, check it out with gh pr checkout, apply the fix, run focused validation like ruff or shellcheck, and push back to the head branch. The Skill only does this when branch ownership and permissions are clear, otherwise it reports suggested fixes.

Can I resolve merge conflicts on someone else's pull request?

Only when GitHub shows the branch is editable by maintainers and the user approves the update. The Skill prefers non-destructive paths like gh pr update-branch or merging the base branch, and never rewrites externally owned history without explicit approval.

Does this work with pull requests from forks?

Yes, fork PRs are supported through gh pr checkout when maintainer modification is allowed. If the fork branch is not writable, the Skill performs a local review and reports findings and suggested changes without claiming upstream resolution.

What happens when a pull request belongs to an Agentic SDLC run?

The Skill switches to findings-and-readiness-only mode: it verifies the local HEAD, recorded promoted_head, and PR head SHA match, then reports readiness without editing, committing, or pushing. Any required change is routed back through the SDLC coordinator gates.

Why does the Skill refuse to rebase a pull request branch?

Rebasing rewrites history, which is unsafe for shared or externally owned branches. The Skill only rebases when the branch is clearly user-owned, the rebase applies cleanly, and it uses --force-with-lease instead of a blind force push.