baidd1011/dsh-code-impact ↗★ 1
dsh-code-impact
Read-only TypeScript and JavaScript change-impact analysis for DeepSeek Harness
安装
npx -p @deepseek-ai/dsh dsh plugin --profile web add github:baidd1011/dsh-code-impact说明文档
阅读完整 README ↗dsh-code-impact
English | 中文
dsh-code-impact is an independent DeepSeek Harness plugin that performs one read-only TypeScript/JavaScript change-impact analysis. It compares a concrete Git change, builds a temporary reverse module graph, and returns changed declarations, affected files, propagation paths, evidence locations, and ranked test candidates. Version 0.2.0 understands JSONC project configuration, tsconfig.json/jsconfig.json, extends, project references, path aliases, package exports/imports, and reuses unchanged snapshot content within one invocation. It does not maintain a repository index.
dsh-code-impact 是一个独立的 DeepSeek Harness 社区插件,用于对一次具体的 TS/JS Git 变更执行只读影响分析。它临时构建反向模块依赖图,返回变更声明、受影响文件、完整传播路径、文件行号证据和排序后的候选测试。0.2.0 支持 JSONC 项目配置、tsconfig.json/jsconfig.json、extends、项目引用、路径别名、package exports/imports,并在一次调用内复用未变化快照内容。不维护长期代码地图。
Install / 安装
npm install dsh-code-impact
dsh plugin --profile demo add dsh-code-impact
dsh --profile demo --dump-config
The package exports cordis.patch.yml through the dsh.bundle.patch manifest field. The patch expects the profile to provide the DSH tools, fs, and subprocess services. It does not install a Git provider or a filesystem provider.
该包通过 dsh.bundle.patch 暴露 cordis.patch.yml。补丁要求 profile 已提供 DSH 的 tools、fs 和 subprocess 服务,不会安装 Git provider 或文件系统 provider。
Tool calls / 工具调用
The registered tool is code_impact。
已注册的工具名为 code_impact。
{"mode":"workspace"}
Compares HEAD with the current working tree, including staged changes, unstaged changes, and untracked non-ignored files.
比较 HEAD 与当前工作树,包含已暂存、未暂存和未被忽略的未跟踪文件。
{"mode":"staged"}
Compares HEAD with the Git index。
比较 HEAD 与 Git index。
{"mode":"refs","base_ref":"origin/main","head_ref":"feature/payment"}
Validates both refs and compares the merge-base to head_ref, which matches the usual pull-request comparison semantics. base_ref and head_ref are rejected in the other modes; an invalid ref never silently falls back to another revision.