What it may solve
把 git Status与仓库规范动态注入 system prompt:分支/脏文件数/最近提交 + 仓库规范指引(官方 system-prompt section/context/variable 缝隙Plugin)
Imported third-party catalog description; not a Registry verification conclusion.把 git Status与仓库规范动态注入 system prompt:分支/脏文件数/最近提交 + 仓库规范指引(官方 system-prompt section/context/variable 缝隙Plugin)
Author: qing3a · Memory · Catalog snapshot: 2026-09-19Canonical semantic path
把 git Status与仓库规范动态注入 system prompt:分支/脏文件数/最近提交 + 仓库规范指引(官方 system-prompt section/context/variable 缝隙Plugin)
Imported third-party catalog description; not a Registry verification conclusion.— stars · 420 downloads
Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19Active analysis coverage 5/5. Historical chains are retained but do not count toward current coverage.
Conclusion: The source structure check completed without finding a structural issue.
Conclusion: The GitHub repository is reachable and not archived. Public data: 1 stars, 34 commits, 0 forks, and 0 watches; latest commit 2026-08-14.
Conclusion: Resolved npm release 0.1.0, published 2026-08-14, license MIT.
Conclusion: Compatibility verification passed. Installation, profile loading, and sustained startup all completed. Test environment: DSH 0.1.6-alpha.2, web profile.
Conclusion: This bounded audit reported 0 known vulnerabilities. It covers only the locked versions and audit source; zero reports is not proof of safety.
The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.
Conclusion: The scan observed 2 code capabilities: declares a prepare script, normally used when building or publishing the package, may start external processes. No predefined elevated-risk condition was triggered; this is not proof of safety.
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: @qing3a/dsh-repo-context@0.1.0; SHA-256: f4e25c3321a0c5f71694953b6fcf0e5247aae4b3406e4b6aff6e5dcd1d92522d.
Automated evidence is scoped to the named artifact, DSH target and profile. It is not a blanket safety or feature-completeness claim.
Describe your task in a DSH conversation and mention @qing3a/dsh-repo-context. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
@qing3a/dsh-repo-contextAnalyzed 0.1.0github:qing3a/dsh-repo-contextExact version not resolved