review-pr

Fetches a Bitbucket pull request, checks out the branch, and produces a full code review report.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/hanh-nd/agent-kit --skill review-pr-hanh-nd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/hanh-nd/agent-kit/tree/main/plugins/agent-kit/.gemini/skills/review-pr
Command: npx skills add https://github.com/hanh-nd/agent-kit --skill review-pr-hanh-nd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a pull request thoroughly requires gathering the PR diff, linked Jira ticket, and the full codebase context, then switching branches safely without losing local work. This Skill automates that entire orchestration so reviewers get a complete, context-aware review without manual setup. ## Core Features & Use Cases - Automated PR Context Gathering: Fetches PR metadata and diffs from Bitbucket, extracts linked Jira tickets, and captures review intent automatically. - Safe Local Checkout: Checks out the PR source branch with dirty-tree and wrong-repo guards, and always restores the original branch afterward, even on failure. - Intelligent Review Routing: Routes diffs to the appropriate review skill (code-review, e2e-review, or both for mixed changes) and assembles a unified report with a PR header. - Use Case: A developer receives a Bitbucket PR linked to Jira ticket PROJ-123. They invoke this Skill with the PR reference, and it fetches the diff, checks out the branch, runs the review, and returns a formatted report with findings and severity levels. ## Quick Start Review pull request 42 from the current Bitbucket repository and give me the full report.

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 Bitbucket pull request with full codebase context?▼

Invoke the review-pr skill with the PR reference. It fetches the PR diff and metadata from Bitbucket, checks out the source branch locally, and delegates the analysis to a code-review skill that can inspect the entire codebase.

How does automated PR review handle Jira ticket context?▼

The skill scans the PR title, description, and branch name for a ticket ID matching the pattern [A-Z]+-\d+, then fetches that Jira ticket. The ticket body becomes part of the intent passed to the review, so findings are judged against the stated goal.

What happens if my working tree is dirty during PR checkout?▼

The skill detects uncommitted changes via git status and marks the checkout as UNHAPPY, skipping the branch switch entirely. It never stashes or forces, and the review proceeds in diff-only mode with a warning appended to the report.

Does the review handle both production code and E2E test changes?▼

Yes. The skill inspects the diff and routes E2E-only changes to an e2e-review skill, production-only changes to code-review, and mixed diffs to both, combining their verdicts into a single report.

Can this skill approve, reject, or comment on the pull request?▼

No. The skill is strictly advisory and never touches the PR itself. It produces a review report for the human reviewer, who makes the final approve or reject decision.