dsh-review

A DeepSeek Harness plugin that adds a code review workflow to /review and /end-review.

/review --deep runs the review as a fleet: one fresh reviewer per lens and file shard scans the change in parallel, then independent adversarial verifier lanes, each blind to the orchestrator and to every other lane, try to break every finding before it reaches the report. With --aggressive, unproven findings are reported as suspicions instead of being withheld.

It reviews uncommitted changes, changes against a base branch, a single commit, a GitHub pull request (checked out locally through gh), or a set of paths as a snapshot. Findings get a priority from [P0] to [P3] and a confidence level. Two kinds of non-blocking notes are kept separate from the fix items: Side Effects & Breaking Changes, and Simplification Opportunities, behavior-preserving cleanups reported with a concrete suggested change.

Install

dsh plugin --profile web add https://github.com/apcamargo/dsh-review.git

The package declares a dsh.bundle manifest, so dsh plugin add enables it as a profile layer automatically. To enable it by hand instead, add the row below to the profile's patch layer, $DSH_HOME/profiles/web/cordis.patch.yml:

- id: review
name: "@apcamargo/dsh-review"

Restart the harness; plugins load at boot. dsh --profile web --dump-config shows the composition.

This release tracks harness 0.2.1-rc.2. Older builds fail the fleet's capability preflight by design.

Quick reference

/review                           # review uncommitted changes (the default)
/review branch []           # base branch by name, or main/master when omitted
/review commit abc123
/review pr 123                    # or a full GitHub PR URL
/review path src docs             # snapshot review, not a diff; @-references work too
/review check the error handling  # any other text becomes the review focus
/review instructions "prefer fail-fast error handling"   # stored for the session; `clear` removes them
/review --deep                    # fleet review: scan, verify, consolidate
/review --deep --aggressive       # fleet review; unproven findings reported as suspicions
/review status
/end-review                       # default: summarize
/end-review fix
/end-review done

Commands

Diff modes require a git repository.

Composer file attachments become snapshot targets: they merge with /review path, and are refused in diff modes, with free-form focus text, and as images.

/end-review [summarize|fix|done]

• summarize (the default) queues a structured handoff: scope, verdict, findings, and an ordered fix queue.
• fix queues a follow-up turn that implements the findings in priority order.
• done clears the session back to ordinary coding work.
• status shows the review state without finishing it.

Findings show up as an ordinary turn, so you can talk to the reviewer while it works.

Deep review (--deep)

Deep review costs many times a regular review and takes much longer. /review --deep [mode] runs three stages through the existing agent loop:

1. Scan. One fresh reviewer per lens (correctness, failure paths, security, contracts, consistency, propagation, simplification; performance opt-in) reviews the change in parallel; large diffs shard the file-local lenses.
2. Consolidate. The orchestrator groups duplicate findings by root cause and drops what does not qualify.
3. Verify. Independent adversarial verifier lanes (reproducer, skeptic, consistency, provenance, impact, fix-auditor, simplifier) judge each finding from one dimension. The lanes read only the stored claims, stripped of reviewer identity and shuffled per lane, so no lane can see another's reasoning.

Only findings the lanes confirm reach the report; contested, inconclusive and unverified ones are withheld as one-liners, and the provenance lane dismisses findings that predate the change or are intentional. The orchestrator copies the verified findings into the report and cannot rewrite them; it also adds a per-finding lane verdict table, coverage, and the Side Effects & Breaking Changes and Simplification Opportunities sections. Simplifications never change the verdict and never enter the fix queue: /end-review fix treats them as informational.

Your typed messages during a deep review reach every worker started after them, and the session's stored instructions, --extra text and project REVIEW_GUIDELINES.md ride to every fleet worker.

Deep review config

Supply the settings with a config: row in the profile patch or your cordis.yml:

- insert:
- id: review
name: "@apcamargo/dsh-review"
config:
deep:
concurrency: 6
callBudgetMs: 900000

Config is validated when the plugin starts and re-checked at /review --deep time, so a bad value fails loudly.