pr-review

Analyze GitHub pull requests and issues for code quality and conflicts.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/fwdarth/agent-teams-lite-domainaware --skill pr-review-fwdarth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/fwdarth/agent-teams-lite-domainaware/tree/main/.opencode/skills/pr-review
Command: npx skills add https://github.com/fwdarth/agent-teams-lite-domainaware --skill pr-review-fwdarth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the process of reviewing GitHub Pull Requests and Issues, ensuring code quality, adherence to project standards, and efficient issue management.

Core Features & Use Cases

  • Automated PR/Issue Listing: Gathers all relevant PRs and issues for review.
  • Project-Specific Convention Analysis: Loads and applies project-specific skills to ensure reviews align with repo standards.
  • Code Quality & Best Practice Checks: Evaluates code for quality, tests, and adherence to best practices.
  • Conflict Detection & Merge Strategy: Identifies potential conflicts and suggests an optimal merge order.
  • Use Case: A developer needs to review a set of pending Pull Requests for a project. This Skill will list them, analyze each against the project's defined conventions and general quality standards, identify any potential conflicts, and provide a clear recommendation on whether to merge, request changes, or reject.

Quick Start

Use the pr-review skill to analyze all open pull requests and issues in the current repository.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I automate GitHub pull request reviews for project conventions?

Automating GitHub pull request reviews involves listing open PRs, evaluating code quality, and checking changes against project-specific conventions to provide actionable merge or rejection feedback.

What is the best way to analyze GitHub issues and pull requests for code quality?

Analyzing GitHub issues and pull requests for code quality requires evaluating the code against best practices, detecting potential conflicts, and generating automated recommendations for merging or closing.

How do I detect merge conflicts across multiple open pull requests?

Detecting merge conflicts across open pull requests is done by analyzing the proposed changes against each other to identify overlapping modifications and suggest an optimal merge order.

Can I enforce project-specific coding standards during a GitHub PR review?

Yes, enforcing project-specific coding standards during a GitHub PR review is possible by loading custom project skills and applying them to evaluate code adherence before merging.

How do I automatically decide whether to merge or reject a GitHub pull request?

Automatically deciding to merge or reject a GitHub pull request relies on evaluating the code against predefined criteria and critical patterns to generate an actionable recommendation.