All plugin categories
DSH Plugin Category

DeepSeek Harness Developer Tools & Plugins

Discover DSH plugins for coding, Git, repository navigation, file operations, debugging, reviews, development workflows, and engineering productivity.

2369 indexed pluginsSorted by popularityPage 54 of 66View newestRecently updated
View plugin dsh-github-sync

dsh-github-sync

minghuo/dsh-github-sync

0GitHub stars
Manifest Valid

把 dsh 会话、插件清单与设置备份到私有 GitHub 仓库(纯 REST,无需 git 二进制),每台机器一个独立目录,可在另一台机器按整机 / 工作区 / 单会话恢复。

DSH Profile: webv0.4.3MIT
View plugin
View plugin dsh-project-nav

dsh-project-nav

Fishsb/dsh-project-nav

0GitHub stars
Manifest Valid

Anti-drift project governance plugin for DSH — bidirectional feature-map, mainline vector, architecture-first protocol | DSH 项目反漂移治理插件

v0.10.4BSD-3-Clause
View plugin
View plugin doco-dsh

doco-dsh

songofhawk/doco-dsh

0GitHub stars
Manifest Valid

DeepSeek Harness native plugin for Doco knowledge base search, block-level reading, outling, and draft saving.

DSH Profile: <name>v0.3.0MIT
View plugin
View plugin dsh-loomy-connect

dsh-loomy-connect

gdrpzym/dsh-loomy-connect

0GitHub stars
Manifest Valid

Use the models that ship with the Loomy desktop app inside DeepSeek Harness — no API key. Also adds a Settings card showing the signed-in account and Loomy credits (permanent + daily gift).

DSH Profile: webv0.2.0MIT
View plugin

About DeepSeek Harness Developer Tools

Developer-tool plugins extend DeepSeek Harness around the day-to-day mechanics of software work. This category covers Git and repository views, file navigation, change review, code references, debugging helpers, development metrics, workspace tooling, build or runtime controls, and automation around common engineering tasks. These plugins are grouped here to make developer-facing capabilities easier to compare without mixing them with unrelated UI or general-purpose extensions.

Developer-tool plugins often operate close to repositories, files, shells, Git operations, and development environments. Before installing one, review its requested capabilities, lifecycle scripts, dependencies, write access, shell behavior, source activity, license, and compatibility evidence. A useful developer plugin should improve the workflow without obscuring what code or system access it requires.