One-click install
npx skills add https://github.com/kaiohenricunha/dotbabel --skill review-pr-kaiohenricunha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/kaiohenricunha/dotbabel/tree/main/plugins/dotbabel/templates/claude/skills/review-pr
Command: npx skills add https://github.com/kaiohenricunha/dotbabel --skill review-pr-kaiohenricunha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually reviewing GitHub pull requests is time-consuming, prone to human error, and often misses critical issues like unresolved review comments, failed CI pipelines, or merge conflicts. This skill automates the entire end-to-end PR review workflow to ensure every PR is thoroughly validated, fixed, and ready for merge without manual overhead.

Core Features & Use Cases

  • Full Comment Triage: Automatically fetches all PR review comments, classifies valid issues versus false positives, and replies to false positives with clear explanations.
  • Isolated Fix Application: Applies fixes for valid review comments in a dedicated git worktree to avoid disrupting the caller's working directory, runs project tests, and pushes changes automatically.
  • Comprehensive Validation: Checks for merge conflicts, failed CI jobs, verifies test plan execution, resolves all review threads, and generates a final status report with merge readiness. Use case: For engineering teams using GitHub, this skill cuts PR review turnaround time by automating repetitive triage, fix, and validation steps, letting reviewers focus on high-impact architectural feedback.

Quick Start

Use the review-pr skill to fully review, fix all valid issues, and resolve all threads for pull request number 42.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I automate GitHub pull request review and fix unresolved comments?

Automating GitHub pull request review involves fetching all PR review comments, classifying valid issues versus false positives, and applying fixes in an isolated git worktree. This workflow automatically replies to invalid comments, runs project tests, and pushes changes without manual intervention.

What's the best way to resolve merge conflicts and failed CI jobs in pull requests?

Resolving merge conflicts and failed CI jobs in pull requests requires comprehensive validation checks. Automated workflows can detect CI failures, verify test plan execution, resolve conflicts, and generate a final status report indicating merge readiness for production-ready PRs.

Can I apply pull request review fixes without disrupting my current working directory?

Yes, applying pull request review fixes without disrupting your working directory is possible using isolated git worktrees. This approach applies fixes for valid review comments in a dedicated environment, runs tests, and pushes changes automatically, keeping the caller's local directory untouched.

Does automated PR review work with existing CI validation and security checks?

Automated PR review works with existing CI validation by checking for failed CI jobs and verifying test plan execution. It integrates security review processes, resolves all review threads, and performs final merge health gating to ensure production-ready PR merges.

Why should engineering teams use automated workflow for pull request management?

Engineering teams use automated pull request management to eliminate manual triage, fix application, and validation overhead. It cuts PR review turnaround time by automating repetitive steps, allowing reviewers to focus on high-impact architectural feedback instead of routine checks.

What are the limitations of automating pull request triage and merge validation?

Limitations of automating pull request triage include potential misclassification of valid issues as false positives during comment analysis. While it handles merge conflicts and CI failures, human reviewers are still needed for complex architectural feedback and nuanced code review decisions.