pr-review

Automate PR reviews for security, quality, and standards issues.

1|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/aronpc/ai --skill pr-review-aronpc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/aronpc/ai/tree/main/skills/pr-review
Command: npx skills add https://github.com/aronpc/ai --skill pr-review-aronpc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR reviews are time-consuming and inconsistent; this skill provides a structured, evidence-based approach to assess changes focusing on security, quality, and adherence to standards, delivering actionable feedback.

Core Features & Use Cases

  • Evidence-based review methodology: multi-aspect analysis of security, quality, and standards conformance across pull requests.
  • Actionable findings: consolidated verdicts with clear remediation steps and follow-up items.
  • Compatibility: tailored for GitHub and GitLab PR workflows with cross-repo applicability.
  • Use case: before merging a PR, run the skill to validate security flaws, code quality concerns, and style adherence, then generate a prioritized list of fixes.

Quick Start

Submit a PR and trigger this skill to generate a structured security, quality, and standards review for the changes.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I automate pull request reviews for security and code quality?

Automate pull request reviews by applying an evidence-based methodology to analyze security, quality, and standards conformance across code changes. This skill processes PR diffs and repository context to produce actionable findings with concrete remediation steps.

Does this code review automation work with both GitHub and GitLab pull requests?

Yes, this code review automation is tailored for both GitHub and GitLab PR workflows. It analyzes pull request diffs and repository context across these platforms to identify security flaws, code quality concerns, and style adherence with cross-repo applicability.

What is the best way to identify security flaws and standards issues before merging a PR?

The best way to identify security flaws and standards issues before merging is running a structured PR review. It applies multi-aspect analysis to validate security vulnerabilities, code quality concerns, and style adherence, generating a prioritized list of fixes.

How do I generate actionable remediation steps from a pull request diff?

Generate actionable remediation steps by submitting your PR diff and repository context to this automated review skill. It consolidates findings into clear verdicts with follow-up items, delivering prioritized and evidence-based feedback for necessary fixes.

What do I need to run an automated PR review for pattern conformance?

To run an automated PR review for pattern conformance, you need access to the pull request diff, repository context, and the ability to reference related skills. No external dependencies are required to analyze your code changes.

When should I not use automated code review for my pull requests?

You should avoid using automated code review when your changes require deep architectural context or business logic validation beyond security, quality, and pattern conformance. This skill focuses on evidence-based findings from PR diffs and may miss nuanced functional requirements.