dsh-chat-diff-summary-legacy: 本轮对话的 Git 变更统计条
`dsh-chat-diff-summary-legacy` 是一款专为 DSH 0.1.5 系列设计的插件，旨在解决开发者查看 Agent 代码变更的需求。它通过实时统计条显示本轮对话的净改动（文件数及增删行数），点击可展开查看具体文件清单。该插件基于快照对比，不修改实际仓库，支持主题自适应，且无需持久化存储。适合 DSH 2.0.13 / 0.1.5 系列内核用户快速确认代码变更。
Read Moredsh-approval-diff: Render Actual Diffs Within the Native Approval Card
`dsh-approval-diff` is a plugin for DeepSeek Harness (DSH) designed to address the limitation of native approval cards, which only display `old_string` and `new_string` without sufficient context. Using the `dsh-diff-view` library, it provides visual code diff review within approval cards, including line-level diffs, word highlighting, line numbers, and source context from disk. The plugin supports toggling between split and unified views and optimizes the batch editing workflow, with features such as diff anchoring, stale operand warnings, and merged multi-file review. It applies only to file-change approval operations. After installation, restart Harness to activate it.
Read Moredsh-patch-edit-plus: Unified Patch Editing Tool for DeepSeek Harness
The `dsh-patch-edit-plus` plugin for DeepSeek Harness (DSH) addresses the low efficiency of line-by-line edits and the difficulty of ensuring atomicity in batch file editing by wrapping a unified `apply_patch` tool. It supports Git unified diff and Codex syntax, with atomic application and zero-byte write capabilities. After installation, parameters such as conflict policy and maximum number of files should be configured in the settings panel. When using it, note that target file directories must already exist and that it relies on a sandboxed execution environment. The plugin is suitable for modifying large files, batch changes across files, and adding or deleting files, effectively balancing development efficiency and security.
Read MoreGit Version Comparison: How to View Code Differences Between Different Versions
Git version comparison is a fundamental and commonly used operation, tracking code changes through diff tools to facilitate collaboration and management. Scenarios requiring version comparison include: locating development errors, checking the staging area before commits, understanding differences before merging branches, and confirming content before rolling back. Common commands and scenarios: 1. Differences between the working directory and the staging area: `git diff`; 2. Differences between the staging area and the most recent commit: `git diff --staged`; 3. Differences between two historical commits: `git diff <commit1> <commit2>` (supports relative commit names like `HEAD~n`); 4. Differences between two branches: `git diff branch1 branch2`; 5. Viewing the content of a single commit: `git show <commit-id>`. Graphical tools (such as VS Code, GitKraken) are suitable for beginners. Mastering commands for different scenarios enables efficient code version management.
Read More