review-pr

Name: review-pr
Availability: InStock
Author: Loopyard

Verify pull requests against project rules in CLAUDE.md.

21|2|Updated Mar 15, 2026

Search Tags:#review #pull-request #tests #pubsub #module-isolation #code-rules

Ready to run

npx skills add https://github.com/loopyard/loopyard --skill review-pr-loopyard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/loopyard/loopyard/tree/main/.claude/skills/review-pr
Command: npx skills add https://github.com/loopyard/loopyard --skill review-pr-loopyard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review PRs against the project's code rules defined in CLAUDE.md to ensure consistency, catch rule violations early, and speed up collaboration.

Core Features & Use Cases

Read the diff to understand changes before applying rules.
Verify tests: ensure new features have tests and bug fixes include reproduction.
Check module isolation and shared state safety to support multiplayer workflows.
Enforce publisher/subscriber contracts and architectural boundaries.
Provide a structured report highlighting violations and suggested remediations.

Quick Start

Submit a PR URL to evaluate it against the project's code rules and receive a structured compliance report.

Frequently Asked Questions about review-pr

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

FAQPage Schema

How do I automate pull request reviews against project code rules?▼

Automating pull request reviews involves checking multi-file diffs against a formal rule set to catch violations early. This process verifies tests, module isolation, and PubSub boundaries, providing a structured compliance report for suggested remediations.

Can I check module isolation and shared state safety in a pull request diff?▼

Yes, checking module isolation and shared state safety in a pull request diff ensures architectural boundaries are maintained. This supports multiplayer collaboration workflows by verifying that new changes do not violate existing publisher and subscriber contracts.

What is the best way to enforce PubSub boundaries and publisher/subscriber contracts?▼

Enforcing PubSub boundaries and publisher/subscriber contracts requires auditing code changes against defined architectural rules. By applying these checks during PR review, you ensure that shared state modifications comply with established project conventions.

Does automated PR review work with a CLAUDE.md rule set?▼

Yes, automated PR review works directly with a CLAUDE.md rule set to evaluate code changes. It reads the diff to understand modifications and applies the defined rules to generate a structured report highlighting any violations and suggested fixes.

How to verify tests for new features and bug fixes during code review?▼

Verifying tests during code review ensures new features include test coverage and bug fixes contain reproduction steps. Automated PR review checks the diff against project rules to confirm these testing requirements are satisfied before merging.

Why does my PR review fail module isolation checks in a multiplayer workflow?▼

PR review fails module isolation checks when code changes violate shared state safety or architectural boundaries defined in the project rules. The structured compliance report highlights these specific violations and provides suggested remediations to fix the broken contracts.