dsh-git-manager
为 DeepSeek Harness 提供 GitHub 联动的可视化 Git 管理:引导式 GitHub Flow 步骤、带 PR/CI 徽章的提交图谱、一键 GitHub 登录、PR 与 issue 管理,以及面向 Agent 的结构化 Git 工具。2.0.0 起由 gitcompass 改名而来。
dayi-z
@dayi-z
⬇ 2
★ 0
master
安装
dsh plugin --profile web add github:dayi-z/dsh-git-manager
需要可复现安装时,可在仓库后追加 #commit 固定提交。
为 DeepSeek Harness 提供 GitHub 联动的可视化 Git 管理:引导式 GitHub Flow 步骤、带 PR/CI 徽章的提交图谱、一键 GitHub 登录、PR 与 issue 管理,以及面向 Agent 的结构化 Git 工具。2.0.0 起由 gitcompass 改名而来。
该插件未提供要点说明,请参考仓库 README。
deepseek-harnessdsh-plugingitgithubgit-panel
- 安装并启动 DeepSeek Harness:
npx @deepseek-ai/dsh web - 在终端执行上面的安装命令(CLI 会解析插件并核验来源)
- 用 dsh plugins list 确认已安装,必要时重启 Harness 生效
插件以当前 dsh 进程的权限运行,安装时可能执行代码。请先通读仓库源码与许可证,确认无破坏性命令与越权访问;本站只做索引,不对第三方插件安全性作担保。
| 代码仓库 | github.com/dayi-z/dsh-git-manager |
| 许可证 | MIT |
| 主要语言 | master |
| 下载量 | 2 |
| GitHub 星标 | 0 |
| 最近推送 | 2026-09-17 |
| 收录日期 | 2026-09-19 |
| 分类 | 开发与运行时 |
事实信息来自公开插件目录快照(2026-10-01),介绍文案由本站再加工。
以下为插件仓库 README 全文(原始内容,由公开目录抓取整理)。
# dsh-git-manager
[English](README.md) | [中文](README.zh.md)
A GitHub-connected visual git manager for [DeepSeek Harness](https://github.com/deepseek-ai/dsh) — guided GitHub-Flow steps, commit graph with PR/CI badges, one-click GitHub login, and structured git tools for the agent.
Its panel chrome is built the way `dsh-better-sidebar` builds its own: every color, type role and motion value rides a DSH theme token, the chrome is flat (hairlines and hover fills, no shadows in the flow), and icon-only controls are round and transparent until hovered. Light/dark and any `dsh-web-ui` skin re-skin the panel for free — the panel contains no palette of its own and no theme selector. See [DESIGN.md](DESIGN.md).
> Renamed from **gitcompass** in 2.0.0. The package, the plugin row id (`dsh-git-manager`), the HTTP routes (`/gitm/*`) and the CSS surface (`--gm-*`) all moved together. The model-facing tool names (`git_status`, `git_commit`, `github_pr_*`, …) are deliberately unchanged — they name the operation, not the product.
## Features
- **Guided Flow Strip** (top bar): visual step indicator through the GitHub-Flow stages: Branch → Commit → Push → PR → Review → Merge.
- **Branch Management**: view local/remote branches, switch, create, delete, rename, merge, fetch, checkout remote.
- **Changes View**: file status (staged/unstaged/untracked), stage/unstage, commit, diff viewer (click any file to see changes), stash/pop, push, pull, fetch.
- **Commit Graph** (GitLens-style lane visualization): 3-column layout (lane / SHA / subject), PR badges, cherry-pick to current, revert commit.
- **PR Management**: list PRs, view detail (checks, reviews, comments), create PR, squash merge, review (Approve / Request Changes / Comment), add comment.
- **Issues**: list issues, view detail, create new issue, add comment.
- **GitHub Integration**: device-flow OAuth login, PAT input, `gh` CLI reuse, encrypted token storage (DPAPI on Windows).
- **Structured Git Tools** (model-side): `git_status`, `git_diff`, `git_branches`, `git_commit`, `git_push`, `github_pr_list/read/create/merge/comment/review`, `github_issue_list/read/create/comment`.
- **Agent Activity Monitor**: a live SSE feed of every agent tool call (start/completion/failure); a repo observer polls workspace state to surface bash git operations performed outside the plugin's tools (new commits / branch switches / working-tree changes).
- **In-Panel Approvals (panel-authoritative)**: write operations pop an approval card inside the panel where you can **Approve** or **Reject** directly; races the native DSH modal — first decision wins. The native channel's automatic rejection (including the ghost deny under approval policy `never`, e.g. the danger-full-access preset) **cannot veto** the panel card — the panel approval path works under any approval policy. Panel decisions are one-shot and memory-only; with no panel connected the call fails fast with a hint to open the panel (or pre-approve the tool there), instead of silently hanging for 5 minutes.
- **i18n**: auto-follows the DSH Web locale (Chinese / English).
- **Theme**: no palette of its own — follows the host theme tokens, so light/dark and third-party skins both apply.
- **Two host modes**: when [`dsh-better-sidebar`](https://github.com/omdsh-dev/DSH-better-sidebar) is installed the panel contributes itself as one of its sidebar tabs and gives up its own column to it; without it the panel keeps its standalone right-column card, now collapsible. See below.
## Install
```sh
dsh plugin --profile web add dsh-git-manager
```
Or for local development:
```sh
dsh plugin --profile web add link:/path/to/dsh-git-manager
```
Restart `dsh web`, open a session bound to a git repository, and the "Git Manager" panel appears in the right-side column.
## Architecture
```
src/
index.ts # Cordis plugin entry: register routes + tools + system prompt
tools.ts # Model-side structured git/GitHub tools (approval race for writes)
core/types.ts # Shared TypeScript types
host/
git-service.ts # Workspace-bounded git operations
routes.ts # /gitm/* HTTP routes (incl. SSE stream /gitm/events, approval endpoint)
event-bus.ts # In-memory event bus + pre-approvals + panel approval broker + repo observer
github-service.ts # GitHub REST wrapper (token never leaves host)
github-auth.ts # Device flow, DPAPI token storage, gh CLI sync
client/
index.ts # Browser entry: picks the host (better-sidebar tab vs standalone)
embed.tsx # better-sidebar tab registration (structural, optional peer)
shell.tsx # Standalone host: the collapsible dock card
Panel.tsx # Main panel: Branches / Changes / Graph / PRs / Issues / GitHub / Agent
styles.ts # The whole stylesheet, on host theme tokens (see DESIGN.md)
api.ts # Typed fetch wrapper over /gitm/* routes
events.ts # SSE subscription + the shared event store behind the tab badge
i18n.ts # Bilingual dictionary (zh/en)
icons.tsx # The single inline-SVG icon source (16px grid, 1.5 stroke)
graph.ts # Commit DAG lane layout algorithm
```
## Host modes
The plugin never claims a surface the host already owns:
- **`dsh-better-sidebar` present** — the panel registers a sidebar tab (`dsh-git-manager:panel`, titled "Git Manager" / "Git 管理", idempotent) and does **not** mount its own column. You open it from the sidebar's new-tab list; it then persists with the session. The tab carries a live badge with the number of write operations waiting for your approval.
- **`dsh-better-sidebar` absent** — the panel keeps its own right-column card, with a collapse handle in its header. Collapsing leaves just that header strip and **stops all polling** (nothing hits git in the background); the state persists.
The detection is a runtime probe (`ctx.get('betterSidebar')`), so better-sidebar stays an *optional* peer: no hard dependency, no build-time import of its types, and a failed registration degrades to the standalone card instead of losing the panel. It can be overruled with `localStorage['gm.host'] = 'dock' | 'tab'` (default: auto).
The panel also **follows the session's workspace**: it resolves the cwd of the session it belongs to (the tab's `scope.cwd`, else the active session), and re-selects the repository whenever you switch sessions — **adding it to the list first if it was never seen** (the host walks up to the innermost repository root, so a session sitting in a nested repo gets that repo rather than the workspace containing it). A repository you picked by hand is never overridden.
### What counts as "the folder I am working in"
A session workspace is often only a **container** — `D:\Harness` holds a dozen independent repositories — so following the session cwd alone can never tell you which one you are actually editing. The host therefore also watches `tools/execute`: it reads the path arguments of the file tools (`read`, `write`, `edit`, `grep`, `glob`, …), walks up to the enclosing repository root, and **auto-registers that repository** into the picker. A file that does not exist yet counts too — the observation happens before the tool runs, so a `write` creating a new file is exactly the case that matters.
- Auto entries are marked and shown as `name · auto` in the picker, so a shelf that grows by itself stays visible instead of mysterious.
- They are capped at **20**; the oldest auto entry is evicted first, and hand-added repositories are never touched.
- `repo:auto-added` is emitted on the activity stream each time one lands.
- Turn it off with `config.autoRegisterRepos: false` on the plugin row — the strip below still reports what is being touched.
A two-line strip under the repo picker is always visible and answers both questions at a glance:
```
Session folder D:\Harness
Editing D:\Harness\dsh-learn-wiki
```
The first line is the session folder the panel follows; the second is the folder the agent is touching **right now** (`Editing` for writing tools, `Reading` for read-only ones). When the second one is a known repository that is not currently selected, a **Switch** button appears beside it.
## Development
```sh
pnpm install
pnpm run build
```
Build output: `lib/` (host) and `client/` (browser bundle).
```sh
node scripts/test-activity.mjs # file-activity auto-registration (isolated temp home)
```
## License
MIT
数据来源:公开的 DeepSeek Harness 插件目录与各插件 GitHub 仓库。本站为独立第三方目录,与 DeepSeek、幻方(High-Flyer)及插件作者均无隶属或背书关系。