Stats
Actions
Tags
From comb
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/comb:help [command-name][command-name]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You print help for the comb plugin.
You print help for the comb plugin.
$ARGUMENTS is empty: print the Overview below verbatim.$ARGUMENTS names a command (review, plan, fix, the-desert, patterns, configure, help): print the matching Per-command entry verbatim.$ARGUMENTS is anything else: print the Overview and add a one-line note: Note: "{argument}" isn't a comb command. Try one of: review, plan, fix, the-desert, patterns, configure.Don't paraphrase. The user is asking for the help text — give them the help text.
comb-the-desert — code-review pipeline for Claude Code
A review → plan → fix workflow with configurable reviewer agents and
authoritative project directives.
Commands
/comb:review Dispatch 1–5 reviewer agents over a PR, branch, file
list, or a spec/design doc. The orchestrator reads the
work first and right-sizes the apparatus: code-shaped
diffs get the full report (verdict, severity scale,
verification); non-code artifacts get a condensed
report (flat findings, no verdict). Read-only.
/comb:plan Turn each review finding into a self-contained fix
instruction file. Read-only.
/comb:fix Execute fix instructions: implementer + reviewer
per item, parallel batching where safe.
/comb:the-desert Run review → plan → fix as one continuous sweep.
Opus everywhere. No pauses, no items skipped. On
non-code artifacts, stops after review — findings go
back into your design conversation, not an autonomous
rewrite pass.
/comb:patterns Scan the codebase and write a PATTERNS manifest of
concrete conventions (structure, naming, closed token
sets, abstraction level, reuse points) with real code
references. Interactive: confirms scan areas first.
review/plan/fix consume it as an observed baseline.
/comb:configure Edit comb.config.json conversationally — paths,
models, enable/disable agents.
/comb:help This message. Pass a command name for details.
Focus brief
Every command accepts free text after the slash. The brief biases
agent picking and finding priority:
/comb:review look for spec/plan misalignment
/comb:the-desert ensure simplicity, scope discipline, TDD coverage
Common workflows
Iterative: /comb:review → review the report → /comb:plan →
approve groupings → /comb:fix
Full sweep: /comb:the-desert (review + plan + fix in one pass)
Config
Layered, deep-merged in this order (later wins):
1. plugin defaults (${CLAUDE_PLUGIN_ROOT}/config/defaults.json)
2. global override (~/.claude/comb.config.json)
3. project override (<project-root>/.claude/comb.config.json)
Edit interactively: /comb:configure
Or hand-edit the JSON files above.
For more on a command: /comb:help <command-name>
/comb:review [scope] [focus brief]
Step 1 of the review → plan → fix workflow.
Inputs
scope A PR number, branch name, or explicit file list.
Defaults to the current branch diffed against
paths.base_branch (default: main).
focus brief Optional free text — biases agent picking and finding
priority.
What it does
- Picks 2–5 reviewer agents based on the diff and the focus brief.
- Dispatches them in parallel against the project's directives.
- Runs typecheck/tests in parallel.
- Consolidates findings into a severity-ranked report.
Output
<paths.reviews>/{pr-N|branch-NAME}-roundN-report.md
Examples
/comb:review
/comb:review 774
/comb:review staging look for spec/plan misalignment
/comb:plan [report-path] [focus brief]
Step 2 of the review → plan → fix workflow.
Inputs
report-path Path to a review report. Defaults to the most recent
report in <paths.reviews>.
focus brief Optional free text — passed through from /comb:the-desert.
What it does
- Parses every finding (including Deferred).
- Suggests groupings for related findings; you decide.
- Dispatches one planner agent per finding (or group) in parallel.
- Each agent reads the actual code and writes a self-contained fix
instruction file.
Output
<paths.plans>/plan-for-<report-stem>/<code>-<title-slug>.md
one file per finding (or group)
/comb:fix [plan-folder] [focus brief]
Step 3 of the review → plan → fix workflow.
Inputs
plan-folder Path to a plan folder produced by /comb:plan.
Defaults to the most recent plan folder.
focus brief Optional free text.
What it does
- Pre-flight: checks the working tree. If dirty, asks once whether
to commit existing changes, stash and restore, proceed without
per-item commits, or abort.
- Executes each fix instruction with implementer + reviewer per item.
- Implementer is agents.implementer (default general-purpose).
- Reviewer specialty is matched to the plan's **Specialty:** header
(was always test-auditor in v0.4.x).
- Reviewer evaluates plan-compliance: did the implementer execute the
plan, and are reported divergences justified?
- Parallel batching where safe; sequential where instructions overlap
in scope.
- Per-item commit on PASS, with the finding code + title in the
message. Opt out via fix.commit_per_item: false.
Trivial-only escape hatch
- After 3 implementer failures on a trivial item, the orchestrator
may apply the fix inline. The reviewer still runs. Standard items
that hit 3 failures escalate to the user.
Models
Trivial fixes: models.fix.implementer_trivial (default: sonnet)
Standard fixes: models.fix.implementer_standard (default: opus)
Reviewer: models.fix.reviewer (default: opus)
Config knobs
fix.commit_per_item (default: true) per-item commit on PASS
agents.implementer (default: general-purpose) the writer agent
/comb:the-desert [scope] [focus brief]
Run review → plan → fix as one continuous sweep, opus everywhere,
no pauses.
Inputs
scope Same as /comb:review.
focus brief Optional free text.
When to use
- High-stakes branches where you want everything done in one pass.
- When you trust the focus brief to do the steering.
When not to use
- When you want a checkpoint between review and plan.
- When you want to hand-pick which findings get instructions.
/comb:patterns [focus brief]
Generate or refresh the PATTERNS manifest — comb's record of this
codebase's concrete conventions, with real file:line references.
What it does
- Recon: detects the codebase's regions (frontend, API, data, etc.)
and flags non-authoritative ones (generated, vendored, reference-
only per CLAUDE.md) to exclude so dead code isn't recorded.
- One scan-plan gate: proposes areas, the directives mapped to each,
and the exclusions — you adjust or reply "go". Flag a stale
directive here to down-weight it.
- Dispatches one read-only scanner per area in parallel, each with
only its relevant directives.
- Synthesizes an area-major manifest with thematic sections
(structural, naming & vocabulary, closed sets, abstraction
calibration, reuse points, error/async, testing).
- If a scanner finds a widespread practice that conflicts with a
directive, walks you through it — record as the new norm, treat
as drift, or skip — and writes your choice into the manifest.
- Pre-write review flags thin/empty areas and lets you re-scan one;
on regenerate, shows a diff to cherry-pick per section.
Output
<paths.patterns> (default: docs/combs/PATTERNS.md)
Consumed by
/comb:review, /comb:plan, /comb:fix — injected as an "observed
baseline" (a prior, not law). Project directives outrank it.
Silence falls back to reading code; deliberate improvements and
new canonical patterns are not flagged as drift.
Config knobs
paths.patterns (default: docs/combs/PATTERNS.md) null disables consumption
models.patterns (default: opus) scanner model
/comb:configure [scope] [change]
Edit comb.config.json conversationally.
Inputs
scope "project" or "global". project edits
<project-root>/.claude/comb.config.json; global edits
~/.claude/comb.config.json. The shipped defaults at
${CLAUDE_PLUGIN_ROOT}/config/defaults.json are not editable.
change What you want different. Examples:
"disable test-auditor"
"use sonnet for plan"
"change reviews dir to docs/reviews"
"look for my directives in docs/our-rules"
What it does
- Shows the merged effective config (so you see what's coming from
where).
- Translates the change into a JSON patch.
- Shows a diff.
- Writes after you confirm.
- Verifies the result parses and the schema is sane.
/comb:help [command-name]
This command. With no argument, prints the overview. With a command
name, prints the deep-dive for that command.
npx claudepluginhub olioskar/comb-the-desert-claude-plugin --plugin combProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.