pr-reviews

Clone repositories, fetch PR metadata, and run parallel review agents.

1|Updated Dec 1, 2016

Search Tags:#code quality #automation #developer tools #code review #pull request #github

Ready to run

npx skills add https://github.com/aaron-vaz/dotfiles --skill pr-reviews-aaron-vaz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-reviews
Source: https://github.com/aaron-vaz/dotfiles/tree/main/opencode/.opencode/skills/pr-reviews
Command: npx skills add https://github.com/aaron-vaz/dotfiles --skill pr-reviews-aaron-vaz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of reviewing pull requests, ensuring thorough analysis of code changes before they are merged.

Core Features & Use Cases

Comprehensive Code Analysis: Utilizes multiple agents to scan for bugs, style issues, and potential improvements.
Contextual Understanding: Analyzes PR intent, blast radius, and relevant repository guidance files.
Use Case: When a developer submits a pull request for a new feature, this Skill can be invoked to perform a detailed review, identify potential issues, and generate a pending review on GitHub for the author to address.

Quick Start

Use the pr-reviews skill to review the pull request with number 123 in the aaron-vaz/dotfiles repository.

Frequently Asked Questions about pr-reviews

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

FAQPage Schema

How do I automate pull request reviews on GitHub?▼

Automated pull request reviews clone the repository, fetch PR metadata, and run multiple review agents in parallel to synthesize findings into a pending GitHub review for the author to address.

Does automated code review work with GitHub Enterprise instances?▼

Yes, automated code review handles GitHub Enterprise instances by fetching PR metadata, performing a deep context scan, and ensuring all required checks pass before posting the synthesized pending review.

What is the best way to analyze code quality and blast radius before merging a pull request?▼

Analyzing code quality and blast radius involves scanning PR intent, invoking domain-specific skills, and running parallel review agents to identify bugs, style issues, and potential improvements before merging.

How do I set up a developer tool to review code changes and post pending reviews?▼

You set up the developer tool by invoking it with the repository name and pull request number, which triggers repository cloning, metadata fetching, context scanning, parallel agent reviews, and pending review posting.

What context does an automated code review scan when checking a pull request?▼

Automated code review scans PR intent, blast radius, and relevant repository guidance files to provide contextual understanding, ensuring thorough analysis of code changes before they are merged.