review-pr

Automate GitHub PR reviews using Irreden-Engine-specific criteria.

8|Updated Oct 11, 2023
One-click install
npx skills add https://github.com/jakildev/IrredenEngine --skill review-pr-jakildev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/jakildev/IrredenEngine/tree/main/.claude/skills/review-pr
Command: npx skills add https://github.com/jakildev/IrredenEngine --skill review-pr-jakildev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the review of GitHub PRs using Irreden-Engine-specific criteria, reducing manual review time and ensuring consistency.

Core Features & Use Cases

  • Dedicated reviewer agent workflow for per-PR analysis, with two-tier model checks (Sonnet and Opus), and stacked PR handling.
  • Generates a structured review covering ownership, ECS invariants, allocation hot paths, naming, tests, and project-specific smells, then posts as a PR comment.
  • Supports PR checkout, in-context diff analysis, and labeling automation.

Quick Start

Ask the reviewer to start by providing a PR number or URL (or say latest) and ensure gh is authenticated, then launch the review agent.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I automate code reviews on GitHub pull requests?

Automated code reviews on GitHub pull requests are handled by a dedicated reviewer agent that checks out the PR, analyzes the diff in context, and posts a structured review comment covering ownership, naming, tests, and project-specific smells.

What is a dedicated reviewer agent workflow for pull request analysis?

A dedicated reviewer agent workflow runs in its own isolated worktree to analyze pull requests without polluting context, utilizing two-tier model checks to evaluate ECS invariants, allocation hot paths, and code quality before posting results.

Do I need gh authentication to run automated PR reviews?

Yes, gh authentication is required before starting. You must also provide a PR number or URL (or use latest) and ensure the reviewer agent is not the PR author to execute the review properly.

Can I use automated code review for stacked pull requests?

Yes, the automated code review process supports stacked PR handling alongside standard pull request checkout and in-context diff analysis to maintain review consistency across dependent changes.

What ECS invariants and allocation hot paths does the PR review check?

The PR review checks ECS invariants and allocation hot paths as part of its structured criteria, ensuring code changes adhere to Irreden-Engine-specific architectural constraints and performance expectations.

Why should the reviewer agent not be the PR author?

The reviewer agent should not be the PR author to maintain an objective review context. This separation ensures the automated analysis evaluates the diff independently without author bias or context pollution.