# AI use cases for DSH Plugin CC (cpj-dev/dsh-plugin-cc) Repo: [cpj-dev/dsh-plugin-cc](https://github.com/cpj-dev/dsh-plugin-cc) | Use cases: 4 | Page: https://dedupedai.com/use-cases/cpj-dev-dsh-plugin-cc/ A Claude Code plugin that runs DeepSeek Harness (dsh) from slash commands for code review, critique, one-shot tasks, and resumable multi-turn sessions. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Get a read-only DeepSeek review of local changes: https://dedupedai.com/use-cases/cpj-dev-dsh-plugin-cc/second-opinion-review-of-local-changes/ - Stress-test a plan or change with a structured critique: https://dedupedai.com/use-cases/cpj-dev-dsh-plugin-cc/adversarial-critique-of-a-plan-or-change/ - Hand a coding task to DeepSeek to run in the background: https://dedupedai.com/use-cases/cpj-dev-dsh-plugin-cc/delegate-a-coding-task-to-run-in-background/ - Keep a multi-turn DeepSeek session going across runs: https://dedupedai.com/use-cases/cpj-dev-dsh-plugin-cc/continue-a-multi-turn-deepseek-session/ ## How to get a read-only DeepSeek review of local changes with DSH Plugin CC Repo: [cpj-dev/dsh-plugin-cc](https://github.com/cpj-dev/dsh-plugin-cc) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Install the plugin and run /dsh:review to get a read-only review of your uncommitted work from DeepSeek. **Who it is for:** A developer in Claude Code who has finished a set of local edits and wants an independent review before committing. **The problem:** Reviewing your own changes often misses the same issues you already overlooked while writing them. **The outcome:** A DeepSeek review of the local changes, produced without write access to the repo. ### Steps 1. Run `/plugin marketplace add cpj-dev/dsh-plugin-cc` in Claude Code. 2. Run `/plugin install dsh@deepseek-dsh`. 3. Run `/dsh:setup` to install the pinned dsh CLI and the multi-turn cc profile. 4. Run `/dsh:review` in the repo, optionally with a focus such as `/dsh:review [focus]`. ### Prompt to paste into your agent ```text In the cpj-dev/dsh-plugin-cc Claude Code plugin, run /dsh:review with focus set to . Return the review text DeepSeek produces. Verify that the review refers to files that actually show local changes in git status. ``` ### Caveat The plugin is POSIX only, so Windows is out of scope, and the README pins @deepseek-ai/dsh at 0.1.1-rc.2. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/cpj-dev-dsh-plugin-cc/second-opinion-review-of-local-changes/ ## How to stress-test a plan or change with a structured critique with DSH Plugin CC Repo: [cpj-dev/dsh-plugin-cc](https://github.com/cpj-dev/dsh-plugin-cc) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Use /dsh:critique to get a structured adversarial critique of a change, design, or approach from DeepSeek. **Who it is for:** A developer or tech lead who has a proposed change or design and wants it challenged before it ships. **The problem:** A proposal that only its author has read tends to hide weak assumptions and untested edge cases. **The outcome:** A structured list of objections and risks from DeepSeek that the author can accept, reject, or act on. ### Steps 1. Run `/plugin marketplace add cpj-dev/dsh-plugin-cc` in Claude Code. 2. Run `/plugin install dsh@deepseek-dsh`. 3. Run `/dsh:setup` once on the machine. 4. Run `/dsh:critique [focus]` with a focus that names the part of the change to challenge. ### Prompt to paste into your agent ```text Using the cpj-dev/dsh-plugin-cc plugin, run /dsh:critique with focus set to . Return the structured critique. Verify that each objection cites a specific part of the change it is about. ``` ### Caveat The README says the plugin needs a DEEPSEEK_API_KEY, and critique output is only as current as the local changes you point it at. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/cpj-dev-dsh-plugin-cc/adversarial-critique-of-a-plan-or-change/ ## How to hand a coding task to DeepSeek to run in the background with DSH Plugin CC Repo: [cpj-dev/dsh-plugin-cc](https://github.com/cpj-dev/dsh-plugin-cc) | Difficulty: Advanced | Time: 45 minutes | Basis: From the README Delegate a task to DeepSeek with /dsh:delegate or /dsh:run --write --background, then check results later. **Who it is for:** A developer who has a well-defined task such as a refactor or a set of fixes and wants to keep working while DeepSeek runs it. **The problem:** Long coding tasks block the main session, and the developer has to wait or switch context. **The outcome:** DeepSeek works on the task in the background, and the developer can list runs and replay the stored result. ### Steps 1. Run `/plugin marketplace add cpj-dev/dsh-plugin-cc` in Claude Code. 2. Run `/plugin install dsh@deepseek-dsh`, then `/dsh:setup`. 3. Run `/dsh:delegate ` for a background handoff, or `/dsh:run --write --background ` if you need write access. (inferred, check the README) 4. Run `/dsh:runs` to list runs, then `/dsh:show ` to replay the stored result. (inferred, check the README) ### Prompt to paste into your agent ```text Using the cpj-dev/dsh-plugin-cc plugin, delegate the task with /dsh:delegate. Then run /dsh:runs and return the run identifier and status. Verify the status before reporting the result. ``` ### Caveat Permissions are fixed before launch with no mid-run approvals, so decide on --write before you start, and a stopped run is killed. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/cpj-dev-dsh-plugin-cc/delegate-a-coding-task-to-run-in-background/ ## How to keep a multi-turn DeepSeek session going across runs with DSH Plugin CC Repo: [cpj-dev/dsh-plugin-cc](https://github.com/cpj-dev/dsh-plugin-cc) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Start a session with --session and continue it with --resume so DeepSeek keeps context across several prompts. **Who it is for:** A developer working through a problem in steps who wants DeepSeek to keep the earlier context. **The problem:** Each fresh one-shot run starts with no memory of the previous one, so every follow-up repeats the setup. **The outcome:** A session id that lets follow-up prompts continue the same DeepSeek conversation while the broker is running. ### Steps 1. Run `/plugin marketplace add cpj-dev/dsh-plugin-cc` in Claude Code. 2. Run `/plugin install dsh@deepseek-dsh`, then `/dsh:setup`. 3. Run `/dsh:run --session ` to start a session. (inferred, check the README) 4. Run `/dsh:run --resume ` to continue it, then `/dsh:runs` to see the session. (inferred, check the README) ### Prompt to paste into your agent ```text Using the cpj-dev/dsh-plugin-cc plugin, start a session with /dsh:run --session on the task , then continue it with /dsh:run --resume on . Return the session identifier and the second response. Verify that the follow-up answer refers to content from the first turn. ``` ### Caveat Session ids live only as long as the broker process, and stopping a mid-turn broker run discards in-memory sessions. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/cpj-dev-dsh-plugin-cc/continue-a-multi-turn-deepseek-session/