peer-review

Review GitHub PR diffs against project rules and merge when accepted.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/ChazzCoin/claude-kit --skill peer-review-chazzcoin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: peer-review
Source: https://github.com/ChazzCoin/claude-kit/tree/main/kit/skills/peer-review
Command: npx skills add https://github.com/ChazzCoin/claude-kit --skill peer-review-chazzcoin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end PR review process by reading the diff, evaluating it against the project's task, craft, and test rules, and taking the corresponding action (approve and merge if accepted; or request changes with concrete comments). The verdict is based on a formal rule-check against the kit's governance contracts and gates, ensuring reviews are consistent and auditable.

Core Features & Use Cases

  • Automated diff evaluation against task-rules.md, craft-rules.md, test-rules.md, and git-flow-rules.md to determine eligibility for merge.
  • Binary, actionable verdicts: accept with merge, or reject with explicit, line-numbered blockers and references to the violating rule.
  • Deterministic merge behavior: posts an approval and merges via GitHub CLI when all checks pass, respecting branch protections and hard gates.
  • Audit trail and rationale: the review includes the specific rules and reasoning that led to the verdict for transparency.

Quick Start

Invoke the peer-review skill on a PR to have Claude read the diff, evaluate it against the project rules, and post an actionable verdict with merge if accepted.

Frequently Asked Questions about peer-review

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

FAQPage Schema
How do I automate GitHub PR reviews against project rules?

Automated PR review evaluates your git diff against project task, craft, and test rules to post a verdict and merge if accepted. It reads the diff, checks scope, gating, and quality, then performs the merge via GitHub CLI when all checks pass.

What is an automated pull request review and how does it work?

Automated PR review fetches the diff and evaluates it against task-rules.md, craft-rules.md, test-rules.md, and git-flow rules. It produces a binary verdict with an audit trail, either merging via GitHub CLI or requesting changes with line-numbered blockers.

Can I automatically merge pull requests when code quality checks pass?

Yes, when all gating, test, and quality checks pass, the review posts an approval and merges via GitHub CLI. This deterministic merge behavior respects branch protections and hard gates defined in your project's governance contracts.

How do I request changes on a PR with actionable feedback?

When a PR fails review, the automation requests changes with explicit, line-numbered blockers and references to the violating rule. This structured feedback provides concrete comments based on the formal rule-check against your project rules.

Does automated code review work with feature, fix, and refactor PRs?

Automated code review applies to typical feature, fix, and refactor PRs across GitHub projects. It evaluates the diff against your kit's governance contracts and gates to determine merge eligibility consistently and transparently.

What are the limitations of automating peer review for pull requests?

Automated peer review requires adopting task-rules.md, craft-rules.md, test-rules.md, and git-flow rules to function. It is designed for typical feature, fix, or refactor PRs and relies on these formal governance contracts to generate its verdict and merge actions.