review-specific-pr

Analyze GitHub pull requests for security and code quality issues.

392|73|Updated Jun 12, 2025
One-click install
npx skills add https://github.com/cnoe-io/ai-platform-engineering --skill review-specific-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-specific-pr
Source: https://github.com/cnoe-io/ai-platform-engineering/tree/main/ui/src/skills/review-specific-pr
Command: npx skills add https://github.com/cnoe-io/ai-platform-engineering --skill review-specific-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables reviewers to systematically assess a GitHub Pull Request by examining code changes, potential bugs, security issues, test coverage, and coding standards.

Core Features & Use Cases

  • Context gathering: fetch PR metadata, diff, CI status, prior reviews, and linked issues
  • Comprehensive analysis: evaluate correctness, security, performance, testing, and style
  • Output: generate a structured review that can be posted as a PR comment or summary

Quick Start

Provide a GitHub PR URL or owner/repo#number to begin the automated review.

Frequently Asked Questions about review-specific-pr

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

FAQPage Schema
How do I automate GitHub pull request reviews for security and correctness?

Automated GitHub pull request reviews analyze metadata, diffs, CI status, and linked issues to evaluate correctness, security, performance, testing, and style. You provide a PR URL or owner/repo#number to receive a structured, security-conscious review with severity levels.

Can I review a GitHub PR using just the repository and number?

Yes, you can review a GitHub PR by providing either the full pull request URL or the owner/repo#number identifier. The review process fetches metadata, diffs, CI status, prior reviews, and linked issues to form a complete analysis.

What does a structured PR code review include?

A structured PR code review includes context gathering from metadata and CI status, comprehensive analysis across correctness, security, performance, testing, style, and architecture, and a final output with severity levels for each identified issue.

Does automated diff analysis check CI status and linked issues?

Yes, automated diff analysis checks CI status, prior reviews, and linked issues alongside the code diff. This context gathering ensures the review reflects build results and original issue requirements before generating the structured output.

What is the best way to perform security-conscious code reviews on pull requests?

The best way to perform security-conscious code reviews is to systematically analyze PR diffs, metadata, and CI status. This approach evaluates security, correctness, and performance while generating a structured review with severity levels that can be posted as a PR comment.

When should I not use automated PR review?

Automated PR review relies on GitHub metadata, diffs, and CI status, so it is not suitable for repositories without accessible pull request data or CI integration. It also serves as an automated assessment rather than replacing final human approval for complex architectural changes.