By olioskar
Comb the Desert: a review → plan → fix pipeline for code review with configurable agents and authoritative project directives.
General code reviewer for diffs and PRs. Hunts bugs, broken contracts, logic errors, data flow issues, and security mistakes. Always-included in comb review palettes when the diff has any code changes.
Checks new work against existing patterns, reference implementations, and approved specs/plans. Catches divergence from established conventions and unstated assumption changes. Selected when the diff touches an area with established patterns or follows a spec/plan worth checking against.
Read-only codebase scanner. Maps one assigned area of a codebase and reports its concrete, established conventions with exact file:line references across structural, naming, closed-set, abstraction, reuse, error-handling, and testing lenses. Generation-only — dispatched by /comb:patterns, never part of a review palette.
Audits error handling for swallowed errors, silent fallbacks, and inadequate failure modes. Selected when the diff contains try/catch blocks, fallbacks, or async flows.
Hunts overengineering, dead code, unclear naming, unnecessary abstractions, and copy-paste duplication in diffs. Selected when the diff introduces abstractions, refactors, new utilities, or non-trivial structural change.
Configure the comb plugin — change paths, swap models, enable/disable agents, edit directive settings. Use when the user wants to configure comb, change comb settings, disable an agent, change which model comb uses, set the base branch, change where reviews are saved, or otherwise tweak `.claude/comb.config.json`.
Execute comb fix instructions sequentially or in parallel batches. Use after /comb:plan has produced instruction files. Each instruction goes to an implementer; standard items also go to a verifier. The user must invoke this explicitly — Claude does not auto-trigger it because it edits code.
Show the comb plugin overview and command list. Use when the user types `/comb:help`, asks "what is comb", "what does comb do", "comb commands", "how do I use comb", or wants a refresher on the plugin. Pass a command name (e.g., `/comb:help fix`) for a deeper look at one command.
Scan the codebase and generate or refresh the PATTERNS manifest — a project-specific record of concrete conventions (structural patterns, naming & vocabulary, closed token/enum sets, abstraction calibration, reuse points, error/async patterns, testing conventions) with real code references. The manifest feeds /comb:review, /comb:plan, and /comb:fix as an observed-baseline context block. Use when the user wants to set up, generate, or refresh comb's project conventions manifest.
Turn comb review findings into per-finding fix instructions. Use after a comb review when the user wants the findings translated into executable fix plans. Each finding gets its own instruction document an implementer can execute cold.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A Claude Code plugin for code review: a /comb:review → /comb:plan → /comb:fix pipeline with /comb:the-desert for the full sweep.
The plugin ships configurable reviewer agents, eight domain-neutral directives, and a layered config system that lets your project policy take precedence.
/comb:review — dispatches 1–5 reviewer agents over a PR / branch / file list / spec doc; right-sizes the apparatus based on what the diff is (code-shaped → full severity-ranked report with verdict and verification; non-code → condensed report with flat labelled findings)/comb:plan — turns each finding into a self-contained fix instruction/comb:fix — executes the instructions, with implementer + reviewer per item, parallel batching where safe; commits each item on reviewer PASS with <code>: <title> (opt out via fix.commit_per_item: false)/comb:the-desert — runs all three steps as one continuous sweep, opus everywhere, no pauses; short-circuits to review-only on non-code artifacts (findings go back to your design conversation, not an autonomous rewrite)/comb:patterns — scans the codebase and writes a PATTERNS manifest of concrete conventions (structure, naming, closed token sets, abstraction level, reuse points) with real file:line references; /comb:review, /comb:plan, and /comb:fix consume it as an observed baseline (a prior, not law)/comb:configure — edit comb.config.json conversationally: change paths, swap models, enable/disable agents, point at your directives/comb:help — overview and per-command details. /comb:help <command> for a deep diveEach command accepts a free-form focus brief that biases agent picking and finding priorities:
/comb:review look for spec/plan misalignment
/comb:the-desert ensure simplicity, scope discipline, and TDD coverage
The plugin is distributed via olioskar/claude-plugins, a marketplace of Claude Code plugins I've authored.
/plugin marketplace add olioskar/claude-plugins
/plugin install comb@olioskar-marketplace
To pull a new release later:
/plugin marketplace update olioskar-marketplace
/plugin uninstall comb@olioskar-marketplace
/plugin install comb@olioskar-marketplace
For local development:
claude --plugin-dir /path/to/comb-the-desert-claude-plugin
After install, in a git repo with some changes:
/comb:review
The plugin picks an agent palette based on what's in the diff, runs the reviewers in parallel, and writes a report to docs/combs/reviews/<derived-name>.md. From there you can /comb:plan to generate fix instructions, then /comb:fix to execute them — or /comb:the-desert to do all three at once.
The plugin reads three layers of config, deep-merged in this order (later wins):
${CLAUDE_PLUGIN_ROOT}/config/defaults.json — shipped defaults~/.claude/comb.config.json — global override<project-root>/.claude/comb.config.json — project overrideIf you'd rather not hand-edit JSON, run /comb:configure and describe the change ("disable test-auditor", "use sonnet for plan", "look for my directives in docs/our-rules"). The skill picks the right scope file, shows a diff, and writes the merged result.
Use a project-specific writer for /comb:fix and /comb:plan:
{
"agents": {
"implementer": {
"subagent_type": "your-org:implementer"
}
}
}
The default is general-purpose (Claude's built-in writer-capable subagent), which is suitable for most projects. Override only if you have a specialist implementer for your stack.
Disable per-item commits (back to v0.4.x behavior):
{
"fix": {
"commit_per_item": false
}
}
Add your team's specialist agents (e.g., a project-local react-expert defined in .claude/agents/react-expert.md):
{
"agents": {
"react-expert": {
"subagent_type": "react-expert",
"when_to_use": "Diff includes React components, hooks, or JSX."
}
}
}
Substitute a shipped role with a specialist plugin's agent:
{
"agents": {
"simplifier": {
"subagent_type": "pr-review-toolkit:code-simplifier"
}
}
}
Point at your team's directives:
{
"directives": {
"user_path": "docs/our-rules"
}
}
Set the role's key to null in an override layer:
{
"agents": {
"simplifier": null
}
}
See config/defaults.json for every supported field. The skill bodies in skills/*/SKILL.md are the runtime contract; CHANGELOG.md documents behavior changes per release.
The plugin ships eight domain-neutral directives at directives/:
npx claudepluginhub olioskar/comb-the-desert-claude-plugin --plugin combHarness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Complete collection of battle-tested Claude Code configs from an Anthropic hackathon winner - agents, skills, hooks, and rules evolved over 10+ months of intensive daily use