set-prompt 0.8.1 → 0.8.2

package/CHANGELOG.md

@@ -4,6 +4,23 @@ All notable changes to this project will be documented in this file.
 
 ---
 
+## [0.8.2] - 2026-05-02
+
+### Fixed
+- **Hermes `register_skill` argument types** — fixed `'str' object has no attribute 'exists'` error that surfaced after enabling the plugin in Hermes. The generated `__init__.py` was passing `str(skill_path)` (the skill directory as a string), but Hermes's `ctx.register_skill(name, path)` expects:
+  1. A `pathlib.Path` object (not a string)
+  2. The path to `SKILL.md` itself (not the parent directory)
+  Verified against the official "Build a Hermes plugin" guide example. Now passes `skill_path / "SKILL.md"` as a `Path`.
+- **Hermes command handler signature** — handler is now defined as `handler(raw_args: str = "") -> Optional[str]` matching the documented Hermes signature (previously `handler(_args=None)`).
+- **Slash commands silent in gateway/TUI mode** — `ctx.inject_message()` is documented as **CLI-mode only** (returns `False` in gateway mode). The handler now falls back to **returning the markdown body** as the command's response when `inject_message` is unavailable, so the content is still visible to the user instead of being silently dropped.
+- **`register_command` now uses keyword arguments** (`handler=`, `description=`) to match the official Hermes plugin examples (e.g. `disk-cleanup`) and stay robust if Hermes reorders positional parameters.
+
+### Notes
+- After upgrading, re-run `set-prompt link hermes` to regenerate `__init__.py`, then restart Hermes. The plugin should now load with `✓ set-prompt v1.0` and skills become loadable via `skill_view("set-prompt:<name>")` (plugin skills are opt-in explicit loads — they do not appear in Hermes's auto-listed `available_skills` index).
+- Hook callbacks remain `def runner(*args, **kwargs)` — Hermes documents that all hook callbacks should accept `**kwargs` for forward compatibility, and the bridge's role is purely to forward the payload to the user-defined hook command via stdin JSON.
+
+---
+
 ## [0.8.1] - 2026-05-02
 
 ### Changed

package/README.md

@@ -123,7 +123,7 @@ The interactive mode shows all agents with their current state. **Check to link,
 
 > **Note on Gemini CLI**: Skills follow the standard `skills/<name>/SKILL.md` pattern. Commands use `.toml` format (not `.md`) and agents use `.md` with YAML frontmatter. Files in your repo's `commands/` must be TOML for Gemini CLI to recognize them. **Agents have strict frontmatter validation** — unknown keys (e.g. `allowed-tools`, `color`, `mode` from other platforms) cause Gemini CLI to reject the agent. See `SET_PROMPT_GUIDE.md` for the allowed keys.
 
-> **Note on Hermes**: Hermes plugins must register skills/commands/hooks programmatically — directory drop-ins are not auto-discovered. set-prompt generates a small Python adapter (`~/.hermes/plugins/set-prompt/__init__.py`) with the repo's absolute path baked in, so no symlinks are needed. **Restart Hermes after `link` (or after adding/removing a skill in your repo)** — `register()` runs only once at Hermes startup. Activation requires `set-prompt` listed under `plugins.enabled` in `~/.hermes/config.yaml` — set-prompt writes this entry automatically (creating the file when absent, or appending to the existing list while preserving other entries and comments via AST-based YAML editing with backup/rollback). Hooks are observation-only on the Hermes side: the same `hooks/hooks.json` is reused, but Hermes events (`pre_tool_call`, `on_session_start`, etc.) are picked up while Claude/Cursor keys are ignored. Hook scripts can reference `${SET_PROMPT_REPO}`.
+> **Note on Hermes**: Hermes plugins must register skills/commands/hooks programmatically — directory drop-ins are not auto-discovered. set-prompt generates a small Python adapter (`~/.hermes/plugins/set-prompt/__init__.py`) with the repo's absolute path baked in, so no symlinks are needed. **Restart Hermes after `link` (or after adding/removing a skill in your repo)** — `register()` runs only once at Hermes startup. Activation requires `set-prompt` listed under `plugins.enabled` in `~/.hermes/config.yaml` — set-prompt writes this entry automatically (creating the file when absent, or appending to the existing list while preserving other entries and comments via AST-based YAML editing with backup/rollback). **Plugin skills are opt-in explicit loads** — they do not appear in Hermes's auto-listed `available_skills` index; load them via `skill_view("set-prompt:<name>")`. Hooks are observation-only on the Hermes side: the same `hooks/hooks.json` is reused, but Hermes events (`pre_tool_call`, `on_session_start`, etc.) are picked up while Claude/Cursor keys are ignored. Hook scripts can reference `${SET_PROMPT_REPO}`.
 
 ---
 

package/dist/index.js

@@ -549,7 +549,7 @@ required_environment_variables:
 
 > **Gemini CLI note**: Only \`name\` and \`description\` are recognized. \`name\` must be lowercase with hyphens and match the directory name.
 
-> **Hermes note (set-prompt integration)**: Hermes does not auto-discover files in standard directories \u2014 plugins must register skills programmatically. set-prompt generates \`~/.hermes/plugins/set-prompt/{plugin.yaml, __init__.py}\` on \`set-prompt link hermes\`. The \`__init__.py\` reads \`<repo>/skills/<skill-name>/SKILL.md\` directly (REPO_DIR is baked in at link time) and calls \`ctx.register_skill()\` at Hermes startup. The skill directory layout is the same as other platforms \u2014 no nested category folder.
+> **Hermes note (set-prompt integration)**: Hermes does not auto-discover files in standard directories \u2014 plugins must register skills programmatically. set-prompt generates \`~/.hermes/plugins/set-prompt/{plugin.yaml, __init__.py}\` on \`set-prompt link hermes\`. The \`__init__.py\` reads \`<repo>/skills/<skill-name>/SKILL.md\` directly (REPO_DIR is baked in at link time) and calls \`ctx.register_skill(name, Path(SKILL.md))\` at Hermes startup. The skill directory layout is the same as other platforms \u2014 no nested category folder. **Plugin skills are opt-in explicit loads** \u2014 they do not appear in Hermes's auto-listed \`available_skills\` index; load via \`skill_view("set-prompt:<skill-name>")\`.
 
 | Field | Required | Platform | Description |
 |-------|----------|----------|-------------|
@@ -659,7 +659,7 @@ Include: 1) Refactored code. 2) Explanation of changes.
 
 #### Hermes commands (set-prompt integration)
 
-Hermes commands are registered programmatically. set-prompt's generated \`__init__.py\` walks \`<repo>/commands/*.md\`, parses each file's YAML frontmatter for \`name\` / \`description\`, and calls \`ctx.register_command(name, handler, description)\`. The handler injects the markdown body as a user message via \`ctx.inject_message(body, role="user")\` when the user invokes the slash command. Hermes does **not** read \`allowed-tools\`, \`model\`, \`agent\`, or other platform-specific frontmatter \u2014 only \`name\` and \`description\` are honored.
+Hermes commands are registered programmatically. set-prompt's generated \`__init__.py\` walks \`<repo>/commands/*.md\`, parses each file's YAML frontmatter for \`name\` / \`description\`, and calls \`ctx.register_command(name, handler=..., description=...)\`. The handler tries to inject the markdown body as a user message via \`ctx.inject_message(body, role="user")\` when the slash command is invoked. **\`inject_message\` is CLI-mode only** \u2014 in gateway/TUI mode it returns \`False\`, and the handler falls back to **returning the body** as the command's response so the content is still visible. Hermes does **not** read \`allowed-tools\`, \`model\`, \`agent\`, or other platform-specific frontmatter \u2014 only \`name\` and \`description\` are honored.
 
 | Field | Required | Platform | Description |
 |-------|----------|----------|-------------|
@@ -2537,8 +2537,18 @@ def _parse_frontmatter(text):
 
 
 def _make_command_handler(ctx, body):
-    def handler(_args=None):
-        ctx.inject_message(body, role="user")
+    # Hermes calls handlers as handler(raw_args: str) -> Optional[str].
+    # Primary path: inject the markdown body as a user message (CLI mode).
+    # Fallback: in gateway mode inject_message returns False \u2014 return the body
+    # as the handler response so the content is at least visible to the user.
+    def handler(raw_args=""):
+        try:
+            ok = ctx.inject_message(body, role="user")
+        except Exception:
+            ok = False
+        if not ok:
+            return body
+        return None
     return handler
 
 
@@ -2607,9 +2617,11 @@ def register(ctx):
         for skill_path in sorted(skills_dir.iterdir()):
             if not skill_path.is_dir():
                 continue
-            if not (skill_path / "SKILL.md").exists():
+            skill_md = skill_path / "SKILL.md"
+            if not skill_md.exists():
                 continue
-            ctx.register_skill(skill_path.name, str(skill_path))
+            # Hermes expects (name, Path-to-SKILL.md), not (name, dir-as-str).
+            ctx.register_skill(skill_path.name, skill_md)
 
     commands_dir = REPO_DIR / "commands"
     if commands_dir.exists():
@@ -2621,7 +2633,11 @@ def register(ctx):
             meta, body = _parse_frontmatter(text)
             name = meta.get("name") or cmd_file.stem
             description = meta.get("description") or ""
-            ctx.register_command(name, _make_command_handler(ctx, body), description)
+            ctx.register_command(
+                name,
+                handler=_make_command_handler(ctx, body),
+                description=description,
+            )
 
     _register_hooks(ctx)
 `;

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "set-prompt",
-    "version": "0.8.1",
+    "version": "0.8.2",
     "description": "One repo. Every AI coding tool. Always in sync.",
     "main": "dist/index.js",
     "bin": {
@@ -31,7 +31,8 @@
         "cursor",
         "codex",
         "opencode",
-        "gemini-cli"
+        "gemini-cli",
+        "hermes"
     ],
     "author": "juncha9 (https://github.com/juncha9)",
     "license": "MIT",