git-pr-review

Review pull requests by analyzing diffs for bugs, security issues, and documentation completeness.

Updated Dec 2, 2025
One-click install
npx skills add https://github.com/qlawmarq/dotfiles-common --skill git-pr-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-pr-review
Source: https://github.com/qlawmarq/dotfiles-common/tree/main/skills/git-pr-review
Command: npx skills add https://github.com/qlawmarq/dotfiles-common --skill git-pr-review

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the code review process, ensuring pull requests meet quality, security, and documentation standards before merging.

Core Features & Use Cases

  • Automated Code Review: Analyzes code changes for bugs, security vulnerabilities, and adherence to best practices.
  • Feedback Generation: Provides structured, constructive feedback to improve code quality.
  • Use Case: When a teammate submits a pull request for a new feature, use this Skill to get a comprehensive review covering code quality, potential issues, and documentation updates.

Quick Start

Use the git-pr-review skill to review pull request number 123.

Frequently Asked Questions about git-pr-review

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

FAQPage Schema
How do I automate code review for a GitHub pull request?

Automating code review for a GitHub pull request involves fetching PR details, analyzing diffs, and checking for code quality, bugs, and security issues to provide structured feedback.

Can I post pull request feedback directly via the GitHub CLI?

Yes, you can post pull request feedback directly via the GitHub CLI. The review process optionally posts structured, constructive feedback to GitHub using the gh command line tool.

Do I need the gh CLI installed to review pull requests?

Yes, you need the gh CLI installed to review pull requests using this approach. The GitHub CLI is a required dependency for fetching pull request details and optionally posting review feedback.

What aspects of code quality are checked during a pull request review?

During a pull request review, code quality checks analyze code changes for bugs, security vulnerabilities, adherence to project conventions, and documentation completeness before merging.

What is the best way to ensure a pull request meets documentation standards?

The best way to ensure a pull request meets documentation standards is to analyze diffs for documentation completeness and adherence to project conventions, generating structured feedback before merging.

Why should I use an automated script for pull request reviews?

You should use an automated script for pull request reviews to streamline the code review process, ensuring changes consistently meet quality, security, and documentation standards before merging.