opencode-command-hooks 0.1.3 → 0.1.4

package/LICENSE

@@ -0,0 +1,19 @@
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,8 +1,6 @@
 # 🪝 OpenCode Command Hooks
 
-Use simple configs to easily integrate shell command hooks with tool/subagent invocations. With a single line of configuration, you can inject a hook's output directly into context for your agent to read.
-
-Example use cases: run tests after a subagent finishes a task, auto-lint after writes, etc. You can also configure the hooks to run only when specified arguments are passed to a given tool. The plugin will handle sequential execution with failure recovery, output truncation, exit code capture, template interpolation, session context injection, toast notifications, toolArgs filtering, and non-blocking error handling.
+Use simple configs to declaratively define shell command hooks on tool/subagent invocations. With a single line of configuration, you can inject a hook's output directly into context for your agent to read.
 
 ## Markdown Frontmatter Hooks
 
@@ -19,6 +17,14 @@ hooks:
 ---
 ````
 
+## Table of Contents
+
+- [Features](#features)
+- [Installation](#installation)
+- [Configuration](#configuration)
+- [Examples](#examples)
+- [Template Placeholders](#template-placeholders)
+
 ### How It Works
 
 1. **Runs automatically** on the configured event
@@ -143,14 +149,14 @@ You can set up tool hooks to only trigger on specific arguments via `when.toolAr
 
 ## Features
 
-- Tool hooks (`before`/`after`) and session hooks (`start`/`idle`)
+- Tool hooks (`before`/`after`) and session hooks (`start`/`idle`) via simple JSON/YAML frontmatter config
   - Hooks are **non-blocking**: failures don’t crash the session/tool.
   - Commands run **sequentially**, even if earlier ones fail.
+- Inject bash output into context with `inject` and notify user with `toast`
   - `inject`/`toast` interpolate using the **last command’s** output if `run` is an array.
-- Match by tool name, calling agent, slash command, and tool arguments
+- Match by tool name and (optionally) arguments
 - Optional session injection and toast notifications
-- Output truncation to keep memory bounded
-- Debug logging via `OPENCODE_HOOKS_DEBUG=1`
+- Automatic output truncation (30,000 by default)
 
 ---
 
@@ -221,7 +227,7 @@ hooks:
 
 ## Examples
 
-### Autonomous Quality Gates (After `task`)
+### Automatically run typecheck, lint, and test (after `task`)
 
 Run validation after certain subagents complete, inject results back into the session, and show a small toast.
 
@@ -304,25 +310,6 @@ Tool-arg matching is exact. This example runs only when the tool arg `path` equa
 }
 ```
 
-### Handle Async Tool Completion (`tool.result`)
-
-```jsonc
-{
-  "tool": [
-    {
-      "id": "task-result-hook",
-      "when": {
-        "phase": "after",
-        "tool": "task",
-        "toolArgs": { "subagent_type": "code-writer" },
-      },
-      "run": ["npm run validate-changes"],
-      "toast": { "title": "Code Writer", "message": "exit {exitCode}" },
-    },
-  ],
-}
-```
-
 ### Session Lifecycle Hooks
 
 ```jsonc
@@ -436,4 +423,4 @@ export const MyHooks: Plugin = async ({ $, client }) => {
     },
   };
 };
-```
+```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-command-hooks",
-  "version": "0.1.3",
+  "version": "0.1.4",
   "description": "OpenCode plugin for declaratively attaching shell commands to agent/tool/slash-command lifecycle events",
   "type": "module",
   "main": "dist/index.js",