Who it is forA developer or tech lead who has a proposed change or design and wants it challenged before it ships.
The problemA proposal that only its author has read tends to hide weak assumptions and untested edge cases.
The outcomeA structured list of objections and risks from DeepSeek that the author can accept, reject, or act on.
What you need first
- Claude Code with plugin support
- Node >= 20 and a DEEPSEEK_API_KEY
- For /dsh:setup: Node >= 22.19, npm, and pnpm (enable with corepack)
- A git repo with local changes to review (for /dsh:review)
Steps
- Run
/plugin marketplace add cpj-dev/dsh-plugin-ccin Claude Code. - Run
/plugin install dsh@deepseek-dsh. - Run
/dsh:setuponce on the machine. - Run
/dsh:critique [focus]with a focus that names the part of the change to challenge.
Prompt for your agent
Using the cpj-dev/dsh-plugin-cc plugin, run /dsh:critique with focus set to <the design or change to challenge>. 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.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for cpj-dev/dsh-plugin-cc and "Stress-test a plan or change with a structured critique"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer