dsh-publish-plugin

Command usage

① /publish-dsh-plugin                  → discover candidates in the session directory (and ancestors / direct subdirectories)
② /publish-dsh-plugin 
         → validate manifest + conflict checks + action summary
③ /publish-dsh-plugin 
 yes     → execute (npm publish + GitHub repo creation/push + tag + topic)

• Without yes it only summarizes, never executes (fail-closed);
• A taken version (already published) reports an error prompting a version bump; an existing package name / repo is treated as a normal upgrade (publish a new version, push to the existing repo);
• Stateless: every step re-discovers and re-checks (conflicts are re-checked right before execution to guard the check→publish gap).

Tool usage

Just ask the model to "publish this plugin". The model calls publish_plugin (plugin_path optional; defaults to the session directory), the tool validates, shows the action summary, and routes the final confirmation through ctx.approval — only allowed-once proceeds. The result returns to the model, which can verify the install, write a CHANGELOG, or handle failures.