review-pr

Review GitHub pull requests for issues and security vulnerabilities.

Updated May 29, 2026
One-click install
npx skills add https://github.com/InnoMikitaKutas/accelerator-test-task --skill review-pr-innomikitakutas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/InnoMikitaKutas/accelerator-test-task/tree/main/.claude/skills/review-pr
Command: npx skills add https://github.com/InnoMikitaKutas/accelerator-test-task --skill review-pr-innomikitakutas

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of reviewing GitHub pull requests, identifying issues, and taking appropriate actions, such as fixing bugs locally or posting comments directly on the PR.

Core Features & Use Cases

  • PR Analysis: Automatically analyze pull requests for bugs, security issues, and code quality problems.
  • Actionable Feedback: Generate a comprehensive review report with findings categorized by severity.
  • User-Specific Actions: Allow users to choose to fix issues locally or post comments directly to the PR.
  • Integration with GitHub CLI: Utilize the GitHub CLI for efficient PR review and management.

Quick Start

Use the review-pr skill to review the pull request with number 42.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I automatically review GitHub pull requests for security vulnerabilities?

To automatically review GitHub pull requests for security vulnerabilities, you can use a code analysis tool that fetches PR metadata and diffs via the GitHub CLI to identify bugs and generate a detailed security report.

Can I post comments directly to a GitHub PR after finding bugs?

Yes, you can post comments directly to a GitHub PR after finding bugs. Code analysis tools can generate actionable feedback and allow you to choose between posting comments to the PR or fixing the issues locally.

Do I need the GitHub CLI to analyze pull request diffs?

Yes, you need the GitHub CLI to analyze pull request diffs. The review process uses 'gh' commands to retrieve PR metadata and diff content, requiring both the 'gh' tool and Python 3 to function.

What is the best way to categorize code quality issues found in a GitHub PR?

The best way to categorize code quality issues found in a GitHub PR is to generate a comprehensive review report that classifies findings by severity, helping prioritize bug fixes and security vulnerabilities.

How do I fix bugs locally after analyzing a GitHub pull request?

To fix bugs locally after analyzing a GitHub pull request, you select the local fix action provided by the PR review tool, which generates a report of findings and allows you to apply the corrections to your local repository.

Does Python 3 work with GitHub CLI for PR review automation?

Yes, Python 3 works with the GitHub CLI for PR review automation. The review process uses Python 3 alongside 'gh' commands to analyze pull request diffs and generate actionable feedback on bugs and vulnerabilities.