ce-code-review

Orchestrate multi-agent code reviews and merge findings into a single report.

2|Updated May 8, 2026
One-click install
npx skills add https://github.com/xotong/claude-marketplace --skill ce-code-review-xotong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-code-review
Source: https://github.com/xotong/claude-marketplace/tree/main/plugins/compound-engineering/skills/ce-code-review
Command: npx skills add https://github.com/xotong/claude-marketplace --skill ce-code-review-xotong

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, git, bash, gh, awk, sed, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Structured, multi-agent code reviews before PR creation, reducing review time by coordinating specialized personas and merging findings into a single, actionable report.

Core Features & Use Cases

  • Dynamically spawns parallel reviewer personas (e.g., correctness, testing, maintainability) to assess code changes.
  • Merges and deduplicates findings into a single report with a stable action path (safe_auto, gated_auto, manual, advisory).
  • Supports PR targets, branch reviews, and standalone checks, with fork-safe base resolution for accurate scope.

Quick Start

Run this workflow on your current checkout to initiate an end-to-end code-review pass before opening a PR.

Frequently Asked Questions about ce-code-review

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

FAQPage Schema
How do I automate multi-agent code review before opening a PR?

Multi-agent code review before a PR is handled by spawning specialized reviewer personas to analyze diffs, merging deduplicated findings into a single actionable report. It coordinates correctness, testing, and maintainability checks to reduce manual review time.

What is the best way to analyze branch diffs for correctness and maintainability?

Analyzing branch diffs for correctness and maintainability is done by orchestrating parallel reviewer personas that assess code changes dynamically. The workflow uses a fork-safe base-resolution script to determine the correct scope and merges findings into a single report.

Does this code review workflow support standalone checks or only PR targets?

This code review workflow supports standalone checks, branch reviews, and PR targets. It uses a fork-safe base-resolution script to accurately determine the review scope across different checkout states.

Do I need git and gh installed to run automated diff analysis?

You need git, gh, jq, bash, awk, and sed installed to run automated diff analysis. These dependencies support the underlying scripts that resolve base branches, extract diffs, and interface with repository tracking systems.

How does multi-agent code review merge findings into an actionable report?

Multi-agent code review merges findings by deduplicating issues from spawned personas into a structured artifact format. The final report provides a stable action path categorized as safe_auto, gated_auto, manual, or advisory.

Can I file residual code review findings as tickets using gh?

Filing residual code review findings as tickets is supported through optional tracker backends using gh. The workflow guides subsequent fixes or ticketing by surfacing residual work identified during the diff analysis.