xiongjiamu/dsh-atomgit
51Last commit Aug 15, 2026
dsh-atomgit DSH plugin
dsh-atomgit bundles AtomGit's three service layers into a single DSH plugin: workflow skills, CLI execution, and an MCP server. After installation, the model gains six built-in skills (plan issues, implement, review/merge PRs, publish releases, mirror to GitHub), native `ag` CLI commands, and `mcp__atomgit__*` tools for repos, branches, issues, PRs, and search. All authentication is unified via a single AtomGit PAT obtained through `ag auth login`.
How to install the dsh-atomgit DSH plugin
dsh plugin --profile web add ./dsh-atomgitCopying does not run this command. Review the repository and version before installing the dsh-atomgit DSH plugin.
dsh-atomgit DSH plugin data source
dsh-atomgit DSH plugin snapshot date: Aug 16, 2026
discovered
What the dsh-atomgit DSH plugin can do
- Provides six built-in AtomGit skills: atomgit-plan-issues, atomgit-implement-issue, atomgit-review-pr, atomgit-merge-pr, atomgit-publish-cli-release, atomgit-mirror-to-github.
- Enables the model to run `ag` CLI commands directly through the bash tool for repo, issue, PR, and release management.
- Bridges AtomGit's platform-hosted MCP server, exposing native tools like `mcp__atomgit__*` without local server setup.
- Unified authentication: one AtomGit PAT (from `ag auth login`) covers all three modules automatically.
- Supports configuration overrides via profile patches, allowing users to disable MCP or point to a custom endpoint.
- Vendored skills from the atomgit-skills upstream, pinned to a tag for reproducible builds.
Where the dsh-atomgit DSH plugin fits
- Automate issue planning and implementation with `atomgit-plan-issues` and `atomgit-implement-issue`.
- Review and merge pull requests using `atomgit-review-pr` and `atomgit-merge-pr` after explicit authorization.
- Publish CLI releases to AtomGit and mirror repositories to GitHub automatically.
- Manage repositories, branches, issues, and PRs through natural language commands via the model.
- Integrate AtomGit operations into larger DSH workflows without leaving the chat interface.
Who the dsh-atomgit DSH plugin is for
- Developers using DeepSeek Harness who want to interact with AtomGit repositories through AI.
- Teams automating code review, release, and mirroring workflows on AtomGit.
- DSH users who prefer a unified plugin with all AtomGit services bundled.
dsh-atomgit DSH plugin limitations
- Requires `ag` CLI installed globally (`npm install -g @hust-open-atom-club/atomgit-cli`) and an initial `ag auth login` for authentication.
- Token fallback (`ATOMGIT_TOKEN` env var) only works when the ag credential file is absent; no GUI-based token management.
- Built-in skills are vendored from a specific upstream tag; updating skills requires running `npm run sync-skills` manually.
- MCP endpoint is platform-hosted – users cannot modify the server logic unless they configure a self-hosted alternative.
- Plugin is designed for the `web` profile; other profiles may require additional configuration.
dsh-atomgit DSH plugin: from the repository README
Quoted from the xiongjiamu/dsh-atomgit README, the upstream source of the dsh-atomgit DSH plugin. Copyright remains with the original authors.
English | [中文](README.zh.md) AtomGit plugin bundle for DeepSeek Harness (dsh): lets dsh users host and manage code on AtomGit out of the box. One package delivers all three AtomGit services: | Layer | Source | Shape in dsh | | --- | --- | --- | | Workflow | [atomgit-skills](https://atomgit.com/hust-open-atom-club/atomgit-skills) | Six built-in skills in the model's `<available_skills>` catalog, loaded on demand via the `skill` tool | | Execution | [atomgit-cli](https://atomgit.com/hust-open-atom-club/atomgit-cli) (`ag`) | The model runs `ag` commands directly through the built-in bash tool | | Interaction | AtomGit platform-hosted MCP server (`https://api.atomgit.com/mcp-server/v1/mcp`) | Native tools `mcp__atomgit__*` bridged by `@deepseek-ai/dsh-mcp-client` over streamable-http; no local server to run | Built-in skills (vendored from the atomgit-skills upstream): `atomgit-plan-issues`, `atomgit-implement-issue`, `atomgit-review-pr`, `atomgit-merge-pr`, `atomgit-publish-cli-release`, `atomgit-mirror-to-github`. ## Installation Prerequisites — **one authentication step covers all three modules**: ```sh # The only setup needed: install ag and log in once. # `ag auth login` sto
Read the full READMEThe repository declares no license. Check with the authors before using it.
dsh-atomgit DSH plugin questions
How do I install dsh-atomgit?
First, install the AtomGit CLI globally: `npm install -g @hust-open-atom-club/atomgit-cli` and run `ag auth login` to authenticate. Then, from the directory containing the plugin package, run `dsh plugin --profile web add ./dsh-atomgit` and start the web interface with `dsh web`. You can also install from a remote source using `dsh plugin --profile web add github:you/dsh-atomgit#<sha>`.
How does authentication work for the three modules?
Authentication is unified. The `ag auth login` command stores an AtomGit PAT in `~/.config/ag-cli/token.json`. The CLI and skills read this file directly. The MCP plugin's `atomgitAuth` service resolves the token from the same file and sends it as `Authorization: Bearer <PAT>` automatically. You can override the token by setting the `ATOMGIT_TOKEN` environment variable in the project's `.env` file, which is used when the ag credential file is absent.
Can I disable the MCP server and use only skills and CLI?
Yes. You can disable the MCP server by adding a patch in your profile configuration. For example, in `cordis.patch.yml` or with a `--patch` overlay, add: `- id: mcp-atomgit` and set `disabled: true`. This will keep the skills and `ag` CLI available while removing the MCP tools.
How do I update the built-in skills to a newer version?
Skills are vendored from the atomgit-skills upstream and pinned to a specific tag. To update to the latest main branch, run `npm run sync-skills`. To update to a specific tag like v1.2.3, run `npm run sync-skills -- v1.2.3`. After syncing, reinstall the plugin to apply the changes.
What if I want to use a different AtomGit MCP server?
You can override the MCP server endpoint by patching the `mcp-atomgit` row in your profile. Set a custom URL in the `config` section, for example: `url: https://your-host/mcp`. You must also inject the `atomgitAuth` service and provide the `Authorization` header using the token from the plugin context. The README provides an example patch for self-hosted servers.