review-prs-ag

Analyze open GitHub pull requests and generate decision-ready reports.

44.0k|5.9k|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/diegosouzapw/OmniRoute --skill review-prs-ag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-prs-ag
Source: https://github.com/diegosouzapw/OmniRoute/tree/main/.agents/skills/review-prs-ag
Command: npx skills add https://github.com/diegosouzapw/OmniRoute --skill review-prs-ag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of silently merging low-quality, insecure, or incomplete changes by systematically reviewing every open pull request and producing a decision-ready report.

Core Features & Use Cases

  • Comprehensive PR discovery: Fetches all open pull requests (with careful handling to avoid truncated results) and gathers titles, authors, diffs, and metadata for review.
  • Critical multi-lens analysis: Evaluates each PR across feature relevance, code quality, security, architecture, global cross-layer completeness, and test coverage.
  • Approval-gated implementation: Pauses for explicit user approval, then (if approved) applies required fixes, runs tests, and merges into the current release branch following strict rules.

Quick Start

Use the review-prs-ag skill to analyze all open PRs in the OmniRoute repository and generate blocking reports for your approval before any merge or integration.

Frequently Asked Questions about review-prs-ag

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

FAQPage Schema
How do I review open GitHub pull requests for security and code quality risks?

To automate pull request review and gate safe merges, this Skill fetches all open PRs with full metadata and diffs, analyzes them for code quality and security risks, and produces a scored verdict with mandatory fixes before pausing for explicit user approval.

What is the best way to enforce release-branch merge rules when reviewing pull requests?

Enforcing release-branch merge rules during pull request review requires applying strict criteria across code quality, security, and test coverage. This Skill generates scored verdicts with mandatory fixes and gates merges into the release branch on explicit user approval.

How does approval-gated implementation work for pull request merges?

Approval-gated implementation pauses all merge actions until explicit user approval is granted. This Skill analyzes open PRs, generates a blocking report with required fixes, and only applies those fixes, runs tests, and merges after receiving explicit user approval.

Can I analyze frontend and backend cross-layer completeness in a GitHub pull request review?

Yes, you can evaluate frontend and backend cross-layer completeness during GitHub pull request review. This Skill applies a critical multi-lens analysis across global cross-layer completeness, architecture impact, and test coverage to ensure changes are fully integrated across all layers.

Why do my automated pull request reviews miss incomplete integrations across backend and frontend layers?

Automated pull request reviews miss incomplete integrations when they lack a critical multi-lens analysis of global cross-layer completeness. This Skill prevents silent merges of incomplete changes by evaluating backend and frontend layers and producing a scored verdict with mandatory fixes.

What should a decision-ready pull request report include to prevent unsafe merges?

A decision-ready pull request report must include a scored verdict, mandatory fixes, and evaluations of code quality, security risks, architecture impact, and test coverage. This Skill generates such reports to gate merges and prevent unsafe or incomplete integrations.