dsh-git-workbench
DeepSeek Harness Git 开发工作台：将 Git 上下文（分支、状态、工作树、存 stash、近期提交）记录到每个会话中，在会话开始时询问要在哪个分支/工作树中进行开发，并切换分支/创建和管理工作树，通
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add dsh-git-workbench@0.3.4Git Workbench 以 dsh-git-workbench 发布，当前版本为 0.3.4。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
A git development workbench for DeepSeek Harness: not a git-status display plugin — it drives the branch/worktree workflow. It captures the repository state (branch, ahead/behind, worktree status, worktrees, stashes, recent commits) into every session, asks which branch or worktree to develop in at new-session start, and switches branches / creates and manages worktrees through /git commands, the git_workbench agent tool, and a Settings page.
autoAsk on, the agent asks once per session which environment to develop in: stay on the current branch, switch to another branch, create a new branch, open an existing worktree, or create a new worktree. The user can skip (stay where they are)./git slash commands
/git status — inject the current git context snapshot/git switch <branch> [--stash|--force] — switch branch/git merge <target> — merge the current branch into /git branch <name> [--from <base>] — create a branch and switch to it/git log [N] — recent commits/git stash [push|list|pop|drop] — stash management/git worktree list · add <branch> [--from <base>] [--dir <path>] · remove <path|branch> [--force] [--delete-branch]git_workbench agent tool — the same guarded operations, callable by the agent (e.g. from the auto-ask flow). Agent-driven switching goes through exactly the same guardrails as the command.git_workbench (action merge, which also handles the target being checked out in another worktree, dirty-tree guards, and already-merged detection), then asks you whether to delete the branch/worktree after the merge or keep it, and only deletes with your explicit choice.needsDecision with options (stash first / force / cancel). Force is gated by allowForceSwitch (default off).--force, gated by allowForceWorktreeRemove (default off). Optionally deletes the branch after removal (--delete-branch, only when merged).execFile with an argument array — no shell, so names cannot inject commands. Branch names are sanitized.autoAsk, ask threshold, worktree directory template ({parent}/{repo}-{branch}), recent-commit count, and the two force toggles. Persisted to $DSH_HOME/git-workbench.json.dsh plugin --profile web add dsh-git-workbench
Slow npm registry?
dsh plugin --profile web add dsh-git-workbench --registry=https://registry.npmmirror.com
Install from a local checkout (development):
dsh plugin --profile web add file:/path/to/dsh-git-workbench
Use the
file:prefix (copies the package intonode_modules). A bareadd .oradd link:…makes pnpm symlink the package, in which case the plugin'sschemasterydependency resolves from the source checkout and is not found — a general pnpm symlink-install gotcha, not a bug in the plugin.
Restart dsh web, then:
/git for the command menu.Worktrees are separate directories, so in DSH each worktree is its own workspace/session. /git worktree add <branch> creates the worktree at <parent>/<repo>-<branch> (configurable via worktreeDirTemplate) and tells you to open a new DSH session in that directory — that is the intended way to "develop in a worktree". The worktree is immediately visible in the worktree list of every other session of the same repository.
@deepseek-ai/* from an out-of-tree host plugin. Declaring @deepseek-ai/dsh-llm / dsh-tools (or any @deepseek-ai/*) as dependencies installs second copies into the profile's node_modules; the resulting duplicate module instances break host module identity (empirically: the tools scheduler's TOOL_RUNTIME_SCHEDULER symbol mismatch makes every tool dispatch fail with Cannot read properties of undefined (reading 'prepare')). This plugin therefore hand-builds its pre-step context message (the createUserMessage shape: id + role:'user' + content + source:{kind:'plugin',plugin,form:'snapshot',sections}, deep-frozen) and registers its agent tool as a plain compiled definition (parameters as an object-rooted JSON Schema with a root required array; output as a strict JsonSchemaNode).dsh-time-context pre-step pattern: ctx.on('agent/pre-step', …, { prepend: true }), fresh capture on step 1, memoized between steps, re-injected when the fingerprint changes or after our own writes.git status --porcelain=v2 does not emit # branch.* header lines unless --branch is passed.npm test # client regression, unit, and real-git integration tests (temp repos)