MIT-licensed DSH plugin that schedules GitHub Trending digests through the local `trendradar` core, renders them in a five-view workbench, and commits each issue to your own repo as a reviewable PR.
DSH integration
Native runtime
Author-claimed
Safety audit
Unaudited
Last verified
2026-11-13
License
MIT
01What can it help you accomplish?
Produce a GitHub Trending digest on a daily / weekly / monthly schedule and land it in your own repository
A digest written byte-for-byte from the core's canonical output, committed to your repo on a branch and opened as a PR — Chinese blurbs and a period summary generated by the local core
Teams and individuals who keep a trending archive repo and want the update to arrive as a reviewable PR instead of a chat answer
Check what the scheduler did without watching a terminal
A workbench with five views: next run and readiness checks on the overview, past daily / weekly / monthly digests rendered as Markdown, and the last 30 runs with their deliverables (commit, content hash, branch, PR link) and logs
DSH users who run the digest unattended and only want to inspect the result
Keep a weekly release summary of a set of repositories next to the trending digest
A per-week Chinese summary of each subscribed repository's new releases, committed on the same branch and PR as the digest, with the subscription list versioned in the data repo
People tracking a fixed set of upstream projects who want release notes folded into the same reviewed PR
02How to install into DeepSeek Harness
Prerequisites
- DSH `0.2.1-rc.3` or newer, Node.js `^22.20.0 || >=24.0.0`
- An existing local git repository with a writable remote — the plugin does not run `git init` for you and reports `REPO_NOT_GIT` otherwise
- git / GitHub credentials for the push and PR step (not needed for a trial run)
- Network access for the core's GitHub fetches; behind a proxy the GUI host usually does not inherit the shell `http(s)_proxy`, so set it in Settings → Core → Network proxy
Installation steps
- 01
Run `dsh plugin --profile <profile> add @morehao/dsh-github-trending`
$ dsh plugin --profile <profile> add @morehao/dsh-github-trending
- 02
Restart the host and open the workbench from the sidebar entry "GitHub 趋势" or Settings → GitHub 趋势
- 03
Point the repository section at the absolute path of your local git repo, pick a provider and model from the DSH provider directory, then do a trial run ("试跑（不提交）") that only fetches and renders — no files written, no commit
Verify the integration
Not specified by the author
03DSH integration and capability boundaries
DSH plugin with a workbench page inside the DSH host: it configures and schedules runs, spawns the local `trendradar` core binary, and renders the resulting digests, run history and subscriptions
Scheduled digest runs via the local trendradar core
a schedule (daily / weekly / monthly), content sources, a model, and a target git repository→a digest committed to your repo on a branch with a PR opened for it
spawns the local `trendradar` core binary as a child processcommits to your repository and opens a PR when push credentials are configuredWorkbench views (overview / digests / runs)
the plugin's own run records and retained preview copies→next-run and readiness panel, Markdown-rendered past digests with a raw toggle, and the last 30 runs with deliverables and read-only logs
GitHub authentication (device-flow login / local gh / PAT)
a GitHub account, an existing `gh auth login` session, or a personal access token→credentials the core can push with; browser-login tokens are kept in the DSH credential record instead of `settings.json`
opens a browser device-code authorization pagestores a PAT as a credential reference or environment variableRelease subscriptions
a list of repositories to watch→a weekly Chinese summary of each repository's new releases, committed with the digest on the same branch and PR
the subscription list is versioned inside the data repositorySummary language control
the digest / subscription summary language setting→summaries in the host language by default (zh → Chinese, en → English), an explicit Chinese / English override, or a Chinese fallback for any other host language
04Who is it for? When not to use it?
Good for
- Teams and individuals who keep a trending archive repo and want the update to arrive as a reviewable PR instead of a chat answer
- DSH users who run the digest unattended and only want to inspect the result
- People tracking a fixed set of upstream projects who want release notes folded into the same reviewed PR
Not for
- The digest itself is produced by the local `trendradar` core, not by the plugin: the binary is downloaded from a GitHub Release on first run and verified by sha256, and several features need a recent core — summary language needs core ≥ 0.12.0, and the proxy setting only takes effect from core ≥ 0.12.4.
- You must supply an existing local git repository (the plugin does not `git init`; a non-repo path fails with `REPO_NOT_GIT`) plus a writable remote and git / GitHub credentials for the push-and-PR step.
- The core fetches GitHub over the network, and a GUI host launched from Finder usually does not inherit the shell proxy, so a direct connection times out; set the proxy in Settings → Core → Network proxy and the plugin injects it into the core subprocess as HTTP(S)_PROXY / ALL_PROXY.
05Compatibility, maintenance and safety notes
- The digest itself is produced by the local `trendradar` core, not by the plugin: the binary is downloaded from a GitHub Release on first run and verified by sha256, and several features need a recent core — summary language needs core ≥ 0.12.0, and the proxy setting only takes effect from core ≥ 0.12.4.
- You must supply an existing local git repository (the plugin does not `git init`; a non-repo path fails with `REPO_NOT_GIT`) plus a writable remote and git / GitHub credentials for the push-and-PR step.
- The core fetches GitHub over the network, and a GUI host launched from Finder usually does not inherit the shell proxy, so a direct connection times out; set the proxy in Settings → Core → Network proxy and the plugin injects it into the core subprocess as HTTP(S)_PROXY / ALL_PROXY.
- A single run is capped by Settings → Core → single-run timeout (300 seconds by default) and the core process is killed when it expires; runs that hit the cap after the machine wakes up are annotated with wall-clock versus active process time.
MIT · latest release v0.9.18 (2026-11-12), README evidence only, safety not audited
06Frequently asked questions
How do I install dsh-github-trending in DeepSeek Harness?
Run `dsh plugin --profile <profile> add @morehao/dsh-github-trending`, restart the host, then open the workbench from the sidebar entry "GitHub 趋势" or Settings → GitHub 趋势. You need DSH 0.2.1-rc.3 or newer, Node.js `^22.20.0 || >=24.0.0`, and an existing local git repository with a writable remote.
Does the plugin generate the digest itself?
No. It is the entry point, not the engine: fetching Trending, parsing, model summaries, rendering and the git / PR steps all run in the local `trendradar` core that the plugin configures, schedules and spawns. The plugin writes the canonical output byte-for-byte and never rewrites, reorders or re-calls the model.
What does it write into my workspace or repository?
Digests and release summaries are committed to the git repository you point it at, on a branch, with a PR opened for review; a trial run writes nothing and commits nothing. The subscription list is versioned inside that data repository, so every issue is auditable and reproducible. Nothing runs in a cloud account — the core runs on your machine and keys only travel to it over a runtime channel, never into a config file or a log.
Why does fetching fail behind a proxy?
A GUI host launched from Finder usually does not inherit the shell `http(s)_proxy`, so the core's GitHub fetches time out and fall back to the GitHub search API. Set the address under Settings → Core → Network proxy and the plugin injects it into the core subprocess as HTTP(S)_PROXY / ALL_PROXY — but only a core ≥ 0.12.4 honours it; older cores connect directly even with the field filled in.
Which language are the summaries in?
The digest language dropdown defaults to following the host UI language (zh → Chinese, en → English) and any other host language falls back to Chinese; you can also pin Chinese or English explicitly. Resolution order is explicit setting > host language > Chinese fallback, and the feature needs core ≥ 0.12.0.
07Related DSH workflows
dsh-our-free-model
by ebony-vinyl
Adds model choices, availability checks, usage panels, and a local OpenAI-compatible forwarder.
dsh-routing-suite
by yjh051108
dsh-routing-suite — injector + router-standard kit: install the runtime injector first, then the task-aware reasoning-mode router preset (measured P1-P23).
dsh-ops
by t-auto
Run Bash and PowerShell commands, search and edit local files, and manage long-running background jobs from DSH.
brooks-lint
by hyhmrright
Portable AI code quality reviews for Codex, Cursor, Copilot and other coding agents: six Agent Skills for architecture, technical debt, tests and remediation.
08Data and sources
GitHub 趋势榜的 **DeepSeek Harness 插件**：按日 / 周 / 月周期定时生成趋势日报，交给本地 [`trendradar`](https://github.com/morehao/trendradar) 核心抓取…
- **它是入口，不是引擎**。抓取、解析、模型总结、渲染、git 与 PR 全在本地 `trendradar` 核心一处实现；插件只负责**配置、调度、spawn 核心、展示结果**，避免两份实现漂移。
工作台从侧栏「GitHub 趋势」或 `设置 → GitHub 趋势` 进入，分五个视图：
This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-11-13. Found an error? Submit a correction.
Best DeepSeek Harness Plugins
Twelve plugins worth installing first — picked from the whole catalog, across every category.