prbot

Generate REVIEW.md with critical issues and file references for pull requests.

3|Updated Sep 5, 2021
One-click install
npx skills add https://github.com/aviralmansingka/dotfiles --skill prbot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prbot
Source: https://github.com/aviralmansingka/dotfiles/tree/main/claude/.claude/skills/prbot
Command: npx skills add https://github.com/aviralmansingka/dotfiles --skill prbot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRs often slip through with hidden bugs, security risks, and design weaknesses that are only caught after merge.

Core Features & Use Cases

  • Critical PR review: Analyzes the PR diff and full context of each changed file to identify bugs, security issues, design problems, edge cases, performance concerns, and maintainability risks.
  • Actionable feedback output: Produces a structured REVIEW.md in the repository root with critical issues, concerns, and suggestions, each including severity, file+line references, and resolution checkboxes.
  • Iterative remediation workflow: Supports addressing issues via /prbot and /prbot resolve until REVIEW.md is resolved, plus PR change and test summarization via /prbot summarize.

Use case: You open a PR that touches multiple modules and want a harsh-but-fair review that pinpoints exactly what to fix before merge and what to watch for if you don’t have time to refactor.

Quick Start

Run /prbot review to generate REVIEW.md with critical issues, concerns, and suggestions for the current pull request.

Frequently Asked Questions about prbot

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

FAQPage Schema
How do I automate code review for a pull request to find bugs and security issues?

Automated code review analyzes your pull request diff and full file context to identify bugs, security risks, and design problems. It generates a structured REVIEW.md file in the repository root with severity levels, file paths, and line references for each issue.

How do I get actionable feedback on my git diff before merging changes?

Actionable feedback on a git diff is produced by evaluating edge cases, performance, and maintainability risks. The review output includes critical issues, concerns, and suggestions with specific file and line references, plus resolution checkboxes.

Can I use a PR review workflow to iteratively resolve code review comments?

Yes, an iterative PR review workflow supports resolving comments by running review and resolve commands until all issues in REVIEW.md are addressed. You can also generate a summary of PR changes and tests using a summarize command.

What's the best way to review pull requests touching multiple modules for maintainability and performance?

Reviewing pull requests across multiple modules requires analyzing the full context of each changed file, not just the diff. This approach pinpoints maintainability and performance concerns, providing harsh-but-fair feedback on exactly what to fix before merge.

Does automated PR review work without external dependencies or API integrations?

Yes, automated PR review works without external dependencies. It operates directly on your repository files, analyzing the changed code context to evaluate design weaknesses and edge cases, then writing the structured review output locally.

When should I not rely on automated code review for my pull requests?

Automated code review should not replace human judgment for complex architectural decisions or nuanced business logic. It is best used to catch hidden bugs, security risks, and maintainability issues that might slip through manual review before merging.