Multi-LLM peer review for code decisions. Bring your own CLI; Chorus convenes 2-4 other LLMs to review the work befor...
Copy the install, test the workflow, then decide if it earns a permanent slot.
The signal is softer here. Treat it like a pattern source unless it solves a very specific gap.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health 100/100. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
Multiple
Model
Claude
Fastest way to find out if chorus belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
git clone https://github.com/chorus-codes/chorus ~/.claude/commands/chorusRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf ~/.claude/commands/chorusNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ │ └─ chorus/ ← installs here ├─ agents/ └─ settings.json
Multi-LLM peer review for code decisions. Bring your own CLI; Chorus convenes 2-4 other LLMs to review the work before you ship.
Source: GitHub repository
Source check: July 18, 2026
Upstream commit: June 1, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.