PR Review

Generate severity-tagged findings, inline comments, and verdicts for pull requests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auto-review open PRs with severity-tagged findings, inline comments, and a one-line verdict to streamline code reviews.

Core Features & Use Cases

  • Severity-tagged, line-specific findings with concise justification for each PR.
  • Inline comments and a one-line verdict to accelerate triage and decisions across repositories.
  • Context-aware review rules including memory context and policy-driven gates to improve review quality.

Quick Start

Run the PR review workflow on an open PR to generate severity-tagged findings and a one-line verdict.

Frequently Asked Questions about PR Review

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

FAQPage Schema
How do I automate code review with severity-tagged findings on open pull requests?

Automate code review by reading PR metadata, diffs, and checks to generate severity-tagged, line-specific findings with concise justifications. The review consults memory and policy context to output structured findings and a one-line verdict suitable for automated posting.

What is the best way to triage high-risk pull requests across multiple repositories?

Triage high-risk pull requests by applying context-aware review rules across multiple repositories to prioritize changes. The automated review generates a one-line verdict and inline comments to accelerate decisions on open PRs.

Can I enforce lightweight quality gates using inline comments on a PR diff?

You can enforce lightweight quality gates by generating inline comments and severity-tagged findings from the PR diff analysis. Policy-driven context is applied during the review to produce structured results for automated posting and human review.

Does automated PR review work without adding external dependencies or components?

Automated PR review works without external dependencies or components. It reads existing PR metadata, diffs, and checks directly, consulting memory and policy context to produce severity-tagged findings and a one-line verdict.

How does diff analysis generate line-specific findings for code review?

Diff analysis generates line-specific findings by evaluating the PR diff against memory and policy-driven context. It outputs concise justifications for each finding, tagged by severity, to accelerate triage and decisions across repositories.