PR Review

Automate GitHub pull request review with risk-tiered triage and merge decision support.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/enuno/noesis-aeon --skill pr-review-enuno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: PR Review
Source: https://github.com/enuno/noesis-aeon/tree/main/skills/pr-review
Command: npx skills add https://github.com/enuno/noesis-aeon --skill pr-review-enuno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the review of open pull requests (PRs) and provides a risk-tiered triage digest, helping developers make informed merge decisions efficiently.

Core Features & Use Cases

  • PR Review: Conducts a deep review of each PR, including severity-tagged findings, inline comments, and a verdict.
  • Risk-Tiered Triage: Generates a digest of PRs sorted by risk and age, allowing prioritization of mergeable PRs.
  • Use Case: Use this Skill to streamline the PR review process in your codebase, ensuring that only high-quality and low-risk PRs are merged.

Quick Start

Run the PR Review Skill with the command: pr-review

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 PR review and risk triage for merge decisions?

Automating GitHub PR review involves analyzing code changes, tagging severity, and generating a risk-tiered digest to prioritize mergeable pull requests. This Skill performs deep code analysis and inline commenting to support efficient merge decisions.

What is risk-tiered triage for pull requests?

Risk-tiered triage for pull requests sorts open PRs by severity, age, and file changes to generate a prioritized digest. This mechanism helps developers identify low-risk mergeable PRs and address high-risk code changes first.

Do I need the GitHub CLI and jq to run automated code analysis on pull requests?

Yes, you need the GitHub CLI (gh) and jq installed to run automated code analysis. The Skill requires GitHub API access to fetch PR data and uses jq to process JSON responses for severity tagging and inline commenting.

How do I prioritize which GitHub pull requests to merge first?

To prioritize GitHub pull requests for merging, you generate a risk-tiered triage digest sorted by severity and age. This approach evaluates file changes and code analysis findings to highlight mergeable PRs with the lowest risk.

Can I get inline comments and severity tagging on GitHub pull requests automatically?

Yes, you can automatically receive inline comments and severity tagging on GitHub pull requests. The Skill conducts deep code analysis on each PR, applying severity tags to findings and posting inline comments directly on the code.

What are the limitations of automating PR review with GitHub API access?

Limitations of automating PR review include dependency on GitHub API rate limits and the necessity of having gh and jq installed. The Skill processes PRs based on severity, age, and file changes, meaning extremely large PRs may impact analysis depth.