chorus-code-reviewer

Reviews an Idea's aggregate code change and posts a structured verdict comment via Chorus MCP.

1.2k|104|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/Chorus-AIDLC/Chorus --skill chorus-code-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chorus-code-reviewer
Source: https://github.com/Chorus-AIDLC/Chorus/tree/main/plugins/chorus/skills/chorus-code-reviewer
Command: npx skills add https://github.com/Chorus-AIDLC/Chorus --skill chorus-code-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Per-task code reviews can each pass while the combined feature is broken; this Skill performs the final read-only review of an entire Idea's aggregate change across all its tasks, catching cross-task integration, security, and regression defects before the feature ships.

Core Features & Use Cases

  • Aggregate feature review: Fetches the Idea, approved proposals, documents, and tasks via Chorus MCP tools, then reviews the whole diff for cross-task integration, architecture drift, security seams, regressions, and feature-level test coverage.
  • Structured verdict output: Classifies findings as BLOCKER or NOTE and posts a single comment on the Idea ending with an exact machine-greppable verdict: VERDICT: PASS, PASS WITH NOTES, or FAIL.
  • Round-aware re-review: In round 2 and later, verifies only whether previous BLOCKERs were fixed without introducing new NOTEs.
  • Use Case: After all tasks of an approved proposal are done, spawn this reviewer to run the project's build and test commands, inspect the combined diff, and post a ship/no-ship verdict on the Idea.

Quick Start

Invoke spawn_agent with the chorus:chorus-code-reviewer skill and the text "Review the code for idea <idea-uuid>. Round: N. Post VERDICT."

Frequently Asked Questions about chorus-code-reviewer

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

FAQPage Schema
How do I run an aggregate code review on a Chorus Idea?

Invoke spawn_agent with the chorus:chorus-code-reviewer skill and a text item like "Review the code for idea <idea-uuid>. Round: N. Post VERDICT." The reviewer fetches the Idea, approved proposals, and tasks via MCP, reviews the combined diff, and posts its verdict as a comment on the Idea.

What is the difference between task review and Idea-level code review?

Task review checks each task in isolation, while this reviewer examines the whole feature's aggregate change. It targets defects only visible when all tasks are seen together, such as broken cross-task integration, contract mismatches, and security gaps at seams.

Can the chorus code reviewer modify files or commit fixes?

No. The reviewer is strictly read-only: it can run test, build, and lint commands plus cat, grep, ls, find, and git diff/log/show, but cannot edit files, install packages, or run git write operations. Fixes are handled by separate fix tasks created by the orchestrator.

What verdicts does the code review produce and how are they classified?

Every review ends with exactly one literal string: VERDICT: PASS, VERDICT: PASS WITH NOTES, or VERDICT: FAIL. Any BLOCKER finding such as build failure, broken integration, or a security hole forces FAIL; only NOTE findings yield PASS WITH NOTES.

How does round 2 code review differ from round 1?

In round 2 and later, the reviewer checks only whether previous BLOCKERs were fixed, re-reading just the affected files and re-running the specific failing tests. It does not introduce new NOTEs on previously unflagged areas.