What it may solve
看得见 Agent 到底改了什么。按会话汇总所有文件改动,一屏审阅后再提交 | See what the agent actually changed. Every file edit in the session, in one review panel.
Imported third-party catalog description; not a Registry verification conclusion.看得见 Agent 到底改了什么。按会话汇总所有文件改动,一屏审阅后再提交 | See what the agent actually changed. Every file edit in the session, in one review panel.
Author: sjh9714 · Sessions & Messages · Catalog snapshot: 2026-09-19Canonical semantic path
看得见 Agent 到底改了什么。按会话汇总所有文件改动,一屏审阅后再提交 | See what the agent actually changed. Every file edit in the session, in one review panel.
Imported third-party catalog description; not a Registry verification conclusion.— stars · 1339 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 could not be confirmed as reachable.
Conclusion: Resolved npm release 0.4.1, published 2026-08-19, license MIT.
Installation and startup verification has not been run.
Dependency audit has not been run.
The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.
Conclusion: The static risk scan could not complete because package validation did not pass.
Conclusion: Package structure or integrity validation did not pass.
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 dsh-what-changed. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
dsh-what-changedAnalyzed 0.4.1github:sjh9714/dsh-what-changedExact version not resolved