AI Agent Hub
Back to plugins
⚙️

dsh-doc-impact

Workflow Updated 2026.08.29

Run the following command in DeepSeek Harness:

dsh plugin install xarleyn/dsh-doc-impact

Paste the following prompt into your AI chat to install this plugin:

Install it in DeepSeek Harness by running dsh plugin install xarleyn/dsh-doc-impact; the repository is hosted at https://github.com/xarleyn/dsh-doc-impact, then restart the harness so the plugin is loaded.

About this plugin

Agents ship code changes every turn, yet the docs that describe those changes are silently left behind. dsh-doc-impact wires code and documentation together in a declarative impact graph, turning the convention of module A changed, doc B must be reviewed into a configurable, automatically enforced rule.

The workflow runs in four beats: at the first step a turn the plugin snapshots a baseline (git HEAD or file content hashes); when the turn is about to stop it diffs the workspace against that baseline and matches the delta against your project rules; a single aggregated reminder is injected so the agent takes one extra model step to review or update the affected documents; in strict modes the agent must explicitly call a resolve tool with a status and reason, and per-fingerprint loop protection prevents endless re-reminders. Four strategies (remind, require-resolution, require-review, require-update), glob include/exclude, and dual git/filesystem detectors are all supported. The plugin ships as a standard Cordis extension with no Harness core patches required, and every setting is toggleable live from the Settings panel.

If your project has an agent touching core modules while API references, architecture notes, and user guides live across the repo, dsh-doc-impact turns doc-sync into an automatic part of every turn, keeping code and documentation in lockstep.

Use Cases

  • After an agent touches core modules, related API docs and architecture notes are auto-scoped for review
  • At turn close, the plugin identifies which documents need updating or review due to code changes
  • Teams want code must ship with docs to be a configurable, enforced process rather than a verbal agreement

Best For

  • Dev teams running agent workflows on DeepSeek Harness
  • Projects with code and scattered docs that need to stay in sync
  • Engineering leads who want doc consistency inside the agent loop