forge-review

Executes tiered GitHub PR reviews with deterministic checks and multi-agent analysis.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/jp5labs/forge-workflow --skill forge-review-jp5labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge-review
Source: https://github.com/jp5labs/forge-workflow/tree/main/forge_workflow/templates/skills/forge-review
Command: npx skills add https://github.com/jp5labs/forge-workflow --skill forge-review-jp5labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manual pull request reviews are inconsistent and slow, especially when trivial changes receive the same scrutiny as complex ones. This Skill automates structured PR reviews on GitHub by scaling review depth to PR complexity, running deterministic checks, validating against linked specs, and posting findings as inline comments and formal reviews. ## Core Features & Use Cases - Tiered Review Depth: Auto-detects Quick, Standard, or Deep tiers from PR size, labels, and file paths, with manual override flags. - Deterministic Checks: Runs in-context checks for missing tests, unbalanced Markdown backticks, and broken path references. - Spec Validation: Detects spec links in linked issues and validates design conformance, constraint compliance, and scope boundaries. - Multi-Agent Deep Review: Dispatches the code-review plugin and a feature-dev security reviewer in parallel for complex PRs. - Use Case: A reviewer runs the skill on PR #42; it auto-detects the Deep tier due to a security label, runs deterministic checks plus a security-focused agent, posts inline comments, and submits a REQUEST_CHANGES review with structured findings. ## Quick Start Ask the AI to review pull request number 42 using the forge-review skill and let it auto-detect the appropriate review tier.

Frequently Asked Questions about forge-review

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

FAQPage Schema
How do I review a GitHub pull request automatically?

Invoke the skill with a PR number, such as /forge-review 42, and it auto-detects the review tier. It gathers PR metadata via the gh CLI, runs deterministic checks, posts inline comments, and submits a formal review as APPROVE, COMMENT, or REQUEST_CHANGES.

How does automatic review tier detection work for pull requests?

Tier detection evaluates labels, changed file paths, and diff size. PRs with security labels, over 300 changed lines, or 10+ files get Deep review; small doc-only changes under 20 lines get Quick; everything else is Standard. Flags like --quick override detection.

Can the review validate a PR against a linked spec document?

Yes. If the PR body links an issue containing a Spec: path line, the skill reads the spec and checks design conformance, constraint compliance, and scope boundaries. Spec findings are posted with blocking or non-blocking severity.

What happens when reviewing a self-authored pull request on GitHub?

GitHub blocks APPROVE and REQUEST_CHANGES on your own PRs. The skill detects this via gh auth status and switches to a configured bot account to submit the review, falling back to a plain comment if no bot account is available.

What are the limitations of the Quick review tier?

Quick tier runs only deterministic in-context checks: missing tests, Markdown backtick balance, and broken path references. It skips the code-review plugin and security agent, so it suits trivial documentation or config changes rather than logic-heavy code.