review-pr

Automate structured GitHub pull request reviews with phase-based workflows.

427|723|Updated Dec 12, 2014
One-click install
npx skills add https://github.com/WikiEducationFoundation/WikiEduDashboard --skill review-pr-wikieducationfoundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/WikiEducationFoundation/WikiEduDashboard/tree/main/.claude/skills/review-pr
Command: npx skills add https://github.com/WikiEducationFoundation/WikiEduDashboard --skill review-pr-wikieducationfoundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Walk through a structured PR review process to standardize and streamline feedback, reduce context switching, and improve review consistency.

Core Features & Use Cases

  • Structured workflow phases: orient, triage, local code checks, and wrap-up to guide reviews.
  • Automated data gathering: fetch PR metadata, CI status, and changed files to inform decisions.
  • Standardized feedback: a repeatable commentary framework with attribution and tone guidelines.

Quick Start

Invoke /review-pr <number> to start the guided PR review session.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I streamline PR reviews and reduce context switching on GitHub?

A structured PR review workflow streamlines feedback by fetching pull request metadata, checking CI status, and surfacing changed files to reduce context switching and standardize reviewer feedback.

What is the best way to standardize code review feedback across a team?

Standardizing code review feedback requires a repeatable commentary framework with attribution and tone guidelines, enforced by guiding reviewers through structured orient, triage, local code checks, and wrap-up phases.

How do I automate GitHub pull request triage sessions?

Automate GitHub pull request triage by initiating a guided review session that automatically gathers PR data, checks CI status, and diffs changed files to inform triage decisions and standardize feedback.

Can I check CI status and diff files before running baseline specs during a code review?

Yes, a phase-based code review workflow fetches PR metadata, checks CI status, and diffs files before running baseline specs, ensuring you validate continuous integration results before proceeding to local code checks.

Do I need to manually fetch PR metadata to start a structured code review?

No, you do not need to manually fetch PR metadata. Invoking the guided review session with a pull request number automatically gathers the required metadata, CI status, and changed files to orient the reviewer.