dsh-ponytail：为 DSH 增加“懒而高效”的代码约束
dsh-ponytail 是一款适用于 DSH 桌面版的 MIT 许可插件，旨在通过注入“极简代码”规则来降低 AI 生成代码时的 Token 消耗。该插件模拟资深工程师思维，优先引导模型复用原生能力、标准库及已有代码，减少非必要的新增依赖和冗余实现。其核心功能包括设置页总开关、输入框内实时档位切换及状态持久化（存储于 `~/.dsh/dsh-ponytail.json`）。插件提供 Off、Lite、Full、Ultra 四档强度，其中 Full 为默认，Ultra 追求最少 Token 和零新依赖。安装支持通过 `dsh` 命令从 GitHub、npm 或本地链接添加，也支持手动克隆仓库并
Read Moredsh-code-reference：DSH 代码参考检索与复用调查插件
dsh-code-reference 是 DeepSeek Harness（DSH）的代码参考检索插件，定位为候选发现器而非自动决策器。它旨在需求澄清后、编码前介入，通过调查本地代码、系统画像及开源平台（GitHub、npm、GitLab、Gitee）中的可复用资源，向用户呈现候选清单与价值权衡。插件由 core、tools、decision 三个模块组成，支持架构级复用及四档决策（直接复用、改造、引入依赖、重写），并依据许可证、语言等政策约束进行自动评估。当前状态为可靠 Beta 版，适用于企业内部试点。安装需固定版本并校验完整性，建议配置 GitHub Token 以提高检索配额。安全方面
Read MoreGit Submodules: The Proper Way to Incorporate Third-Party Code into Your Project
Git submodules are used to address issues such as version control loss, collaborative chaos, and code redundancy when a parent project reuses third-party code. The core idea is to embed an independent sub-repository within the parent project, which only records the location and version information of the submodule, facilitating independent tracking of updates. Basic usage: After initializing the parent project, use `git submodule add` to add a third-party repository as a submodule (generating the `.gitmodules` file to record configurations). When cloning a parent project containing submodules, use `--recursive` or manually execute `git submodule update` to pull the submodule code. Submodules can be modified and updated independently, while the parent project needs to commit new references to the submodule to synchronize versions. Note: Submodules do not update automatically; you need to manually enter the submodule directory, execute `git pull`, and then commit the parent project. For multi-person collaboration, `.gitmodules` and submodule versions must be shared to ensure consistent paths and versions. Submodules differ from subtree merging, where the former is maintained independently, while the latter merges code into the parent project.
Read MoreA Guide to Git Submodules: Managing Dependent Code in Projects
Git submodules are tools for reusing independent code (such as common libraries) in large projects, solving problems like duplicate copying and version synchronization. Core advantages include: space savings through code reuse, independent maintenance for easy modification and submission, and version specification by the main project to ensure consistency. Essentially, submodules are independent Git repositories, with the main project recording configurations and version references via .gitmodules and .git/config. Core usage steps: Add submodules to the main project using `git submodule add`; clone projects with submodules using `--recursive`, otherwise use `init+update`; commit main project references after modifying submodules; update with `git submodule update`; clean configurations when deleting submodules. Common issues: Empty repositories after cloning (supplement with `--recursive` or `update`), unupdated main project after submodule modifications (supplement with commits), version conflicts (agree on branches). Summary: Suitable for independently reusable dependencies, following the process: add → clone/update → modify and commit → update main project references, improving maintenance efficiency.
Read More