pr-reviewer

Analyze GitHub pull request diffs for security, error handling, and style issues.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/MMXC/openclaw-back --skill pr-reviewer-mmxc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-reviewer
Source: https://github.com/MMXC/openclaw-back/tree/main/workspace/skills/pr-reviewer
Command: npx skills add https://github.com/MMXC/openclaw-back --skill pr-reviewer-mmxc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, python3, golangci-lint, ruff, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of reviewing GitHub pull requests, identifying potential issues before human review.

Core Features & Use Cases

  • Automated Code Analysis: Analyzes code diffs for security vulnerabilities, error handling gaps, style violations, and missing test coverage.
  • Lint Integration: Integrates with linters like golangci-lint and ruff for deeper code quality checks.
  • Structured Reports: Generates clear, categorized reports detailing findings.
  • Use Case: When a developer submits a pull request, this Skill can automatically check for common mistakes, security risks, and style inconsistencies, providing immediate feedback and reducing the burden on human reviewers.

Quick Start

Use the pr-reviewer skill to check all unreviewed open pull requests in the current repository.

Frequently Asked Questions about pr-reviewer

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

FAQPage Schema
How do I automate GitHub pull request code reviews for security and style issues?

Automating GitHub pull request code reviews involves analyzing code diffs for security vulnerabilities, error handling gaps, and style inconsistencies. This Skill integrates with linters to check Go, Python, and JavaScript/TypeScript, generating structured reports to reduce human review burden.

Does automated PR review work with Python and Go projects?

Automated PR review works with Python and Go projects by integrating with specific linters. It uses ruff for Python code quality checks and golangci-lint for Go, analyzing diffs to identify style violations and missing test coverage.

Do I need the gh CLI to run automated code analysis on pull requests?

You need the gh CLI authenticated with repository access to run this automated code analysis. It relies on the gh CLI to fetch pull request data and diffs directly from GitHub for subsequent security, style, and coverage checks.

What is the best way to check unreviewed open pull requests in a repository?

The best way to check unreviewed open pull requests is using an automated review Skill. It evaluates code diffs for security risks, error handling, and style issues, then generates categorized reports detailing all findings for immediate feedback.

Can I use linters like ruff and golangci-lint for deeper code quality checks on GitHub PRs?

You can use linters like ruff and golangci-lint for deeper code quality checks on GitHub PRs. This Skill integrates directly with these tools to analyze pull request diffs, identifying style violations and security vulnerabilities automatically.