review-pr

Analyze GitHub pull requests against CDP architecture standards and draft inline review comments.

3.4k|728|Updated Jun 28, 2022
One-click install
npx skills add https://github.com/linuxfoundation/crowd.dev --skill review-pr-linuxfoundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/linuxfoundation/crowd.dev/tree/main/.claude/skills/review-pr
Command: npx skills add https://github.com/linuxfoundation/crowd.dev --skill review-pr-linuxfoundation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill standardizes PR reviews by automating the collection of PR metadata, diffs, and prior inline comments, enabling consistent, thorough feedback aligned with CDP architecture standards.

Core Features & Use Cases

  • Fetches PR title, base/head branches, author, files changed, and diff summary for quick assessment.
  • Validates PR metadata (title format, JIRA key presence, branch naming) against living rules in .claude/rules/ while reading the guard-protected-files hook for protected paths.
  • Runs a code-standards enforcer in the background to identify violations across changed files without posting any comments automatically.
  • Drafts inline review comments with suggested fixes and a concise review summary for user approval before any action on the PR.

Quick Start

Provide a PR number and optional instructions, then review the automatically generated draft in the terminal and approve or refine before posting.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I automate GitHub PR review against architecture standards?

Automated PR review against architecture standards is done by fetching pull request metadata, full diffs, and prior inline comments to validate changes. A background code-standards enforcer checks for violations and drafts suggested fixes for terminal approval before posting.

Can I validate PR metadata like branch naming and JIRA keys automatically?

PR metadata validation for branch naming, title format, and JIRA key presence is handled automatically. The review process checks these attributes against living rules configured in the `.claude/rules/` directory to flag any deviations.

How do I draft inline code review comments with suggested fixes before posting?

Drafting inline review comments with suggested fixes happens automatically in the terminal after analyzing the diff. The system presents a concise review summary and generated comments for your approval or refinement before any action is taken on the pull request.

Does PR review automation check for changes to protected file paths?

PR review automation does check for changes to protected file paths by reading guard-protected-files hook configurations. This ensures that modifications to sensitive files are flagged during the validation process alongside code-standards enforcement.

What is the best way to enforce code-standards checks on a pull request diff?

The best way to enforce code-standards checks on a pull request diff is running a background enforcer that identifies violations across changed files. It collects metadata and drafts inline comments with fixes for user approval without posting automatically.