gh:review

Coordinate parallel reviewer personas to analyze code diffs and generate structured findings.

2|1|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI --skill gh-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh:review
Source: https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI/tree/main/plugins/galeharness-cli/skills/gh-review
Command: npx skills add https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI --skill gh-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinating thorough code reviews across multiple reviewer personas to surface structured, governance-driven findings before merging.

Core Features & Use Cases

  • Spawns parallel reviewer personas that analyze diffs for correctness, security, performance, and maintainability.
  • Merges and deduplicates findings into a single, actionable report with ownership routing.
  • Supports interactive, autofix, report-only, and headless modes for automation and CI pipelines.

Quick Start

Run gh:review on the target PR or branch to generate a structured, multi-agent code review report before merging.

Frequently Asked Questions about gh:review

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

FAQPage Schema
How do I automate multi-agent code reviews before a PR merge?

To automate multi-agent code reviews before a PR merge, this Skill coordinates parallel reviewer personas to analyze diffs and outputs a consolidated report with structured findings.

What is structured diff analysis for cross-cutting validation in code changes?

Structured diff analysis for code changes evaluates correctness, security, performance, and maintainability by spawning parallel reviewer personas that merge and deduplicate findings into a single actionable report.

Can I run automated code review reports in a headless CI pipeline?

You can run automated code review reports in a headless CI pipeline using the headless mode, which supports automation and outputs structured findings with run artifacts without interactive prompts.

Does the multi-agent code review process support autofix and report-only modes?

The multi-agent code review process supports interactive, autofix, report-only, and headless modes, allowing you to generate governance-driven findings and route ownership based on your workflow needs.

What do I need to provide to generate a pre-PR code review report?

To generate a pre-PR code review report, you need to provide a target PR or branch diff and ensure the configuration includes a YAML frontmatter with name and description fields.

When should I use parallel reviewer personas for code changes?

Use parallel reviewer personas for code changes when you need cross-cutting validation across correctness, security, performance, and maintainability, especially for pre-PR diffs and post-task iterations.