dsh-agent-extension
用于工作区命令、技能和路径范围规则的 DeepSeek Harness 插件。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:SugarFatFree/dsh-agent-extension#3dd07e4dff4df10c64f300ac8785f8cdcbd67211Agent Extension 以 dsh-agent-extension 发布，当前版本为 0.1.5。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
点击下方 Badge 复制 Markdown，粘贴到 README 即可。
验证 package.json 声明的 GitHub 仓库，即可管理这个公开页面。认领后，Hub 会优先安排当前版本的安全扫描，并在通过后公开展示结果。
认领这个 Plugin →A DeepSeek Harness (DSH) plugin that discovers reusable Markdown slash commands, skills, and path-scoped rules from a project and the current user's configuration directories.
.dsh and .agents directory conventions.web profile.pnpm, which DSH uses for profile plugin management.Install directly from GitHub with DSH's native plugin command:
dsh plugin --profile web add github:SugarFatFree/dsh-agent-extension
DSH recognizes this package as a plugin because its package.json declares dsh.bundle.patch. The command installs it into the selected profile and adds it to dsh.profile.bundles automatically.
Restart the DSH Web process and refresh the browser after installation. Create a new session or resume an existing one to refresh its slash-command catalog.
This project is currently distributed from GitHub only; it is not published to npm. GitHub installation is fully supported and does not require an npm account:
dsh plugin --profile web add github:SugarFatFree/dsh-agent-extension
A future npm release may provide a shorter package-name install command, but npm publication is optional and does not affect DSH compatibility or catalog listing.
From this repository directory:
dsh plugin --profile web add .
After changing a local file: dependency, run pnpm install --force from the Web profile directory to refresh its installed node_modules copy, then restart DSH Web.
For a session, the project root is the nearest ancestor containing .git. If none exists, the session working directory is used.
| Type | Project roots | User roots |
|---|---|---|
| Commands | <project>/.dsh/commands/**, <project>/.agents/commands/** | ~/.dsh/commands/**, ~/.agents/commands/** |
| Skills | <project>/.dsh/skills/**, <project>/.agents/skills/** | ~/.dsh/skills/**, ~/.agents/skills/** |
| Rules | <project>/.dsh/rules/**, <project>/.agents/rules/** | ~/.dsh/rules/**, ~/.agents/rules/** |
Definitions may be nested up to six levels. For example, .agents/skills/team/review/SKILL.md and .dsh/commands/release/prepare.md are discovered.
When definitions conflict, the first result wins in this order:
.dsh.agents~/.dsh~/.agentsCommands use their command name as the conflict key. Skills use their skill name. Rules use their relative path below the relevant rules directory.
Each Markdown file under a commands root becomes a slash command. Its name is resolved from YAML frontmatter name, then an H1 such as # /release - Release, then the filename.
---
name: release
description: Prepare a release
---
Read the release checklist and prepare the release notes.
Entering /release optional arguments starts a normal agent turn with the command body and supplied arguments as task instructions.
Command roots are watched for Markdown additions, edits, deletions, and nested directory changes. After adding .agents/commands/aa.md, an already-open session receives /aa without restarting DSH Web; the command menu updates through DSH's live command-change event. Refresh the browser only if its connection was interrupted.
A skill is either a Markdown file or a directory bundle containing SKILL.md. Skills require standard YAML frontmatter with a kebab-case name and description.
---
name: api-review
description: Review API compatibility
whenToUse: Before publishing a changed API
---
Review the changed API surface.
The optional disable-model-invocation, user-invocable, and metadata frontmatter fields are passed through to DSH. Skills are exposed through DSH's Skills catalog and / skill source, not the command-only source; unreadable files in one discovery root are skipped so they do not hide skills from other roots.
A rule is a Markdown file under a rules root whose YAML frontmatter contains a non-empty paths list. Markdown files without paths, including README.md, are ignored.
---
name: frontend-conventions
paths:
- "code/frontend/**"
- "web/**"
---
Use the established component and accessibility conventions.
A matching rule is injected once, immediately before the next model step after the agent successfully reads, writes, or edits a matching workspace file. Patterns are evaluated relative to the project root.
Run the built-in command in an agent session:
/dsh-extension-status
It reports the calling session's working directory plus discovered commands, skills, and rules. Discovered project commands are registered in the session command directory and appear in the / menu.