orchestrate-review

Runs a review-only pipeline on existing branch changes via the orchestrate engine.

1|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/williamthorsen/codeassembly --skill orchestrate-review-williamthorsen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrate-review
Source: https://github.com/williamthorsen/codeassembly/tree/main/packages/agents/content/skills/orchestrate-review
Command: npx skills add https://github.com/williamthorsen/codeassembly --skill orchestrate-review-williamthorsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code written manually or by non-orchestrated agents never passes through the full review cycle, leaving defects, simplification opportunities, and holistic issues undetected before merge. ## Core Features & Use Cases - Review-only pipeline: Invokes the orchestrate engine with a single review-cycle phase covering parallel review, code-simplification-reviewer, and holistic review, skipping architecture, planning, and implementation. - Configurable review behavior: Supports --max-review-rounds, --diff-base, --approval-threshold, and --budget-threshold arguments to control iterative review depth and severity gating. - Use Case: After manually fixing findings from a run that exited with needs_manual_review, invoke this skill to re-run the full review cycle against the branch diff without repeating development phases. ## Quick Start Ask the agent to run the orchestrate-review skill on the current branch with a task description explaining what the changes accomplish.

Frequently Asked Questions about orchestrate-review

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

FAQPage Schema
How do I run a code review cycle on an existing branch?

Invoke the orchestrate-review skill with a task description of what the branch changes accomplish. It validates the branch has a diff against the diff base, then runs the orchestrate engine's review-cycle phase with parallel review, code-simplification-reviewer, and holistic review.

When should I use orchestrate-review instead of orchestrate-dev?

Use orchestrate-review when code already exists and only needs review, such as manually written code or re-review after manual fixes. Use orchestrate-dev when you need the full workflow including architecture, planning, and implementation phases.

Can I control how many review rounds run?

Yes, pass --max-review-rounds=N to cap iterative review rounds (default 3). You can also set --approval-threshold and --budget-threshold to low, medium, or high to control which finding severities must be fixed or consume remaining budget.

Why does the review fail with no changes to review?

The skill runs git diff against the merge base resolved from --diff-base or the project's default branch and exits if the diff is empty. Ensure your branch contains commits relative to the diff base and that a non-empty task description is provided.

What are the limitations of a review-only pipeline?

It cannot generate architecture, plans, or implementations, so it only works on branches that already contain changes. It also requires a task description for reviewer context and a resolvable diff base to compute the change set.