DeepSeek Harness Plugin Hub

发布与管理完整 Harness Profiles,发现适合你的插件。

探索

插件目录环境预设文档中心动态

社区

发布插件联系我们报告问题

相关链接

Plugin Hub GitHubDeepSeek Harness 官方项目系统状态隐私说明
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

独立、非官方社区项目,与 DeepSeek 官方无隶属、授权或背书关系。

Tool Reading Map — DeepSeek Harness 插件(DSH Plugin)
DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录
← Plugins
T

dsh-tool-reading-map

Tool Reading Map

用于 DeepSeek Harness 的代码仓库阅读地图工具:在智能体编辑代码之前,为任何代码库提供结构化、按优先级排序的地图

插件会安装到这里;不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add github:he-yufeng/dsh-tool-reading-map#fad5988a9371eb580a88f4ae7be2975eedcd9f51
README兼容性版本

兼容性与来源证明

Tool Reading Map 以 dsh-tool-reading-map 发布,当前版本为 0.1.0。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

DSH 兼容范围
*
运行环境
any
发布来源
github
Registry 更新时间
2026/9/14

版本

0.1.0stable
2026/9/14

相关插件

正在加载相关插件…

最新版
0.1.0
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
未提供
文件数
未提供
Surface
any
许可证
MIT
发布源
github
GitHub
★ 0
周下载
0
最近提交
2026/9/14
查看源码 ↗
README Badge

点击下方 Badge 复制 Markdown,粘贴到 README 即可。

这是你的 Plugin?认领权益 · 优先安全扫描

验证 package.json 声明的 GitHub 仓库,即可管理这个公开页面。认领后,Hub 会优先安排当前版本的安全扫描,并在通过后公开展示结果。

认领这个 Plugin →
报告问题

相关插件

继续浏览 developer-tools 分类下经过校验的插件。

Doctor@linxin666/dsh-doctorDSH 配置档案的事务性救援模式,配备受监督的启动器、隔离的恢复容器、确定性修复、健康监控以及本地 Web 恢复控制台Ssh@linxin666/dsh-sshdsh Web GUI 的远程 SSH 操作:主机配置存储(~/.dsh/dsh-ssh.json,可从 ~/.ssh/config 导入)、支持跳板主机的持久化 ssh2 连接池、exec / PTY Web 终端 / SFTP 传输 / 本地端口转发隧道 / 集群执行Tui@deepseek-harness-tui/dsh-tui用于 DeepSeek Harness 智能体、会话和工具的交互式终端界面。DSCODE@toddzheng024/dscode-bundle完整的 DeepSeek 编码代理,支持持久化 shell、Ultra 协作和自动权限审查。

README

dsh-tool-reading-map

English | 中文

A reading_map tool plugin for DeepSeek Harness (dsh). Before the agent edits an unfamiliar codebase, give it a structured, priority-ranked map of the repo instead of letting it wander file by file.

What it does

One model-facing tool, reading_map:

  • Priority-ranked file list — config files and entrypoints first, source code before docs, each entry with language, role (config / entrypoint / code / other), line count, size, and a bounded preview. Config and entrypoint files are kept whole.
  • Honest coverage account — every run reports how many candidate files existed, how many were kept, which directories were skipped, and which files were dropped for being oversized, binary, minified, or over the file cap. A partial map never pretends to be complete.
  • Deterministic — the scan never calls a model. It is cheap, fast, and identical on replay; the agent summarizes from the map itself when it wants prose.

The ranking and skip heuristics are ported from RepoWiki's scanner, battle-tested on thousands of repos.

Install

dsh plugin --profile <name> add github:he-yufeng/dsh-tool-reading-map

or from npm (once published):

dsh plugin --profile <name> add dsh-tool-reading-map

Boot the profile and the tool appears as reading_map alongside the built-ins.

Tool reference

ParameterTypeRequiredDefaultMeaning
pathstringyes—Absolute path of the repository root to scan.
max_filesnumberno60Files kept after priority ranking (config > entrypoint > code > other).
preview_linesnumberno30Preview lines kept per non-config, non-entrypoint file.
max_file_sizenumberno204800Per-file size cap in bytes; larger files are counted as oversized and skipped.

The result is one canonical JSON value: { root, coverage: { candidates, kept, skippedDirs, oversizedCount, oversized, binaryCount, minifiedCount, priorityDropped }, files: [...] }, so it composes cleanly with PTC mode and other tooling.

What gets skipped, in one table:

SkippedHow it is detected
Dependency / build dirsnode_modules, dist, build, vendor, .venv, target, caches, and more (see SKIP_DIRS in src/scanner.ts)
Assets and lock/binary extimages, media, archives, fonts, compiled artifacts, .map, .min.js, .lock
Oversized fileslarger than max_file_size (counted, first three named)
Binary filesNUL byte within the first 8 KiB
Minified sourcesingle line over 1000 chars, or ≤5 non-empty lines with a giant longest line
.gitignore pathsroot .gitignore globs (no negation support, by design)

Real output (run against the RepoWiki repo)

Reading map of /path/to/RepoWiki: kept 60/78 candidate files, 15 dirs skipped, 12 dropped by priority.
- [config] .env.example (text, 14 lines)
- [config] frontend/package.json (json, 33 lines)
- [config] frontend/tsconfig.json (json, 22 lines)
- [config] frontend/vite.config.ts (typescript, 20 lines)
- [config] pyproject.toml (toml, 81 lines)
- [config] README.md (markdown, 181 lines)
- [config] src/repowiki/config.py (python, 94 lines)
- [entrypoint] src/repowiki/__main__.py (python, 6 lines)
- [entrypoint] src/repowiki/server/app.py (python, 158 lines)
- [code] frontend/src/App.tsx (tsx, 19 lines)
- [code] frontend/src/components/MermaidDiagram.tsx (tsx, 50 lines)
- [code] frontend/src/components/SettingsModal.tsx (tsx, 79 lines)
… and 48 more in the structured result.

Skipped on this run (the honest part): .git, .venv, dist, frontend/node_modules, every __pycache__, plus 12 lower-priority files dropped past the cap — all named in coverage, never silently missing.

Development

npm install
npm run build     # tsc -> lib/
npm test          # vitest

Layout:

src/
  index.ts    # plugin entry: name / inject / apply
  tool.ts     # reading_map tool definition
  scanner.ts  # the walk, ranking, skip rules, and coverage accounting
test/
  scanner.test.ts

Load it from a checkout during development with a patch overlay (absolute path):

- insert:
    - id: reading-map
      name: /absolute/path/to/dsh-tool-reading-map/lib/index.js

pnpm dsh web --patch ./cordis.dev.yml

License

MIT