review

Orchestrate parallel specialist agents to review GitHub pull requests and save findings.

1|2|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/joi-fairshare/agentic-workflow --skill review-joi-fairshare
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/joi-fairshare/agentic-workflow/tree/main/skills/review
Command: npx skills add https://github.com/joi-fairshare/agentic-workflow --skill review-joi-fairshare

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill orchestrates multi-agent pull request reviews so you can automatically triage diffs, spawn domain experts, and collect structured findings without managing each reviewer yourself.

Core Features & Use Cases

  • Automated triage: Reads PR metadata and diffs to assign specialist agents using a dedicated triage prompt.
  • Parallel reviewer dispatch: Launches every reviewer simultaneously with tailored prompts so each focus area is evaluated in isolation yet recorded centrally.
  • Persistent review records: Consolidates reviewer outputs, blocks for investigations when needed, and saves the response file in the repo’s agentic-workflow review directory for later publishing via postReview or implementation with addressReview.

Quick Start

Trigger /review with the PR reference to coordinate all specialist agents and store their findings.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate multi-agent pull request reviews on GitHub?

Multi-agent PR review works by reading pull request metadata and diffs to assign specialist agents, who evaluate changed files simultaneously in isolation. It uses a dedicated triage prompt to dispatch reviewers and consolidates their structured findings into a persistent local report.

What is the best way to triage GitHub PR diffs with domain-specific expert agents?

The best way to triage PR diffs with expert agents is using a dedicated triage prompt that reads PR metadata and dispatches parallel domain-specific reviewers. Each specialist evaluates isolated focus areas, recording structured findings centrally for comprehensive evaluation.

Can I save persistent review records locally when evaluating GitHub pull requests?

You can save persistent review records locally by consolidating reviewer outputs into a response file stored in the repository's agentic-workflow review directory. This ensures review data remains accessible for later publishing or implementation.

Does multi-agent PR review support investigation handoffs during the audit trail?

Multi-agent PR review supports investigation handoffs by blocking the review process when needed and integrating triage with reviewer prompts. This maintains a structured audit trail, ensuring all findings and handoffs are recorded in the persistent local review report.

How do I publish structured PR review findings after parallel specialist agents finish?

Publishing structured PR review findings after parallel specialist agents finish is done using the postReview command on the saved persistent review records. Alternatively, addressReview can implement the collected findings from the local agentic-workflow directory.