skill-git-review-standards

Define GitHub Pull Request review standards for quality, size, and communication.

2|Updated Feb 12, 2026

Search Tags:#git #workflow #code review #pull request #github #quality

Ready to run

npx skills add https://github.com/RyoMurakami1983/skills_repository --skill skill-git-review-standards

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: skill-git-review-standards
Source: https://github.com/RyoMurakami1983/skills_repository/tree/main/archive/skill-git-review-standards
Command: npx skills add https://github.com/RyoMurakami1983/skills_repository --skill skill-git-review-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses inconsistent and time-consuming code review processes by establishing clear standards for PR quality, size, and communication.

Core Features & Use Cases

Define Review Objectives: Clarify what reviewers must check.
Set PR Size Standards: Establish limits for efficient reviews.
Implement Review Checklists: Ensure consistency in checks.
Establish Feedback Style Rules: Promote respectful and effective communication.
Define Approval Policies: Clarify necessary approvals and SLAs.
Detect Anti-Patterns: Prevent rubber-stamping and drive-by approvals.

Quick Start

Use the skill-git-review-standards to define clear review goals, size limits, and communication rules for reliable PR reviews.

Frequently Asked Questions about skill-git-review-standards

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

FAQPage Schema

How do I establish consistent standards for GitHub pull request reviews?▼

Standardize PR reviews by defining review objectives, setting PR size limits, implementing review checklists, and establishing respectful feedback style rules. This solves inconsistent practices and delayed approvals by enforcing shared ownership.

What is the best way to prevent rubber-stamping and drive-by approvals in code reviews?▼

Prevent rubber-stamping and drive-by approvals in code reviews by implementing strict approval policies and utilizing anti-pattern detection. Defining clear review objectives enforces evidence-based decisions over superficial approvals.

How do I set PR size limits for efficient code reviews?▼

Set PR size limits for efficient code reviews by establishing standards that keep pull requests small. Small PRs are a core principle that reduces review time, improves feedback quality, and accelerates the approval workflow.

Why does defining review objectives improve pull request feedback quality?▼

Defining review objectives improves pull request feedback quality by clarifying exactly what reviewers must check. This enforces evidence-based decisions and respectful communication, directly addressing ineffective feedback and delayed approvals.

Can I use these code review standards to manage feedback style and communication protocols?▼

Yes, you can use these code review standards to manage feedback style and communication protocols. They establish rules for respectful feedback and shared ownership, ensuring effective communication across GitHub pull requests.