review-orchestrated

Name: review-orchestrated
Availability: InStock
Author: ccam80

Automate code review against specs and fix mechanical violations.

Updated Feb 21, 2026

Search Tags:#automation #developer tools #quality assurance #code review #refactoring #cleanup

Ready to run

npx skills add https://github.com/ccam80/claude-orchestrator --skill review-orchestrated

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-orchestrated
Source: https://github.com/ccam80/claude-orchestrator/tree/main/skills/review-orchestrated
Command: npx skills add https://github.com/ccam80/claude-orchestrator --skill review-orchestrated

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the code review process by automatically identifying and fixing mechanical violations, ensuring code quality and consistency before manual review.

Core Features & Use Cases

Automated Review: Spawns reviewer agents to check completed implementation against specs and rules.
Violation Classification: Distinguishes between mechanical (auto-fixable) and non-mechanical violations.
Mechanical Fixes: Automatically removes dead code, comments, and other non-essential elements.
Use Case: After a development wave, run this skill to clean up any stray comments or dead code, presenting only the significant issues that require human judgment.

Quick Start

Use the review-orchestrated skill to review all completed phases in the project.

Frequently Asked Questions about review-orchestrated

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

FAQPage Schema

How do I automate code review and cleanup after a development wave?▼

Automating code review involves spawning parallel reviewer agents to check completed implementations against project specifications, classifying violations, and automatically fixing mechanical issues like dead code removal so only significant problems require human judgment.

What is the best way to automatically remove dead code and stray comments before manual review?▼

Automatically removing dead code is handled by classifying violations into mechanical and non-mechanical categories, where mechanical violations like stray comments are auto-fixed with user confirmation, leaving only complex issues for manual review.

Do I need structured project specifications and progress tracking to use automated code review?▼

Yes, structured project specifications and progress tracking are required. The automated review process validates completed implementations against these defined rules and spec files to accurately identify mechanical violations and ensure consistency.

How does automated code review distinguish between auto-fixable violations and issues needing human judgment?▼

Automated code review distinguishes violations through a classification mechanism that separates mechanical violations, which are auto-fixed, from non-mechanical violations that require human judgment, ensuring developers only review significant code quality issues.

Can I run automated code cleanup across multiple completed project phases at once?▼

Yes, you can run automated code cleanup across multiple completed project phases. The tool spawns parallel reviewer agents per phase, consolidates the findings, and automatically fixes mechanical violations across the entire implementation.