From f65ab491be3b748502566e179c63235bffe878da Mon Sep 17 00:00:00 2001 From: Hawthorn Date: Wed, 10 Jun 2026 18:21:12 +0530 Subject: [PATCH] fix(docs): clarify Stop event matcher is optional, not disallowed MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Validator (scripts/ci/validate-hooks.js line 182-184) only errors when matcher is missing for non-EVENTS_WITHOUT_MATCHER events. For Stop (in EVENTS_WITHOUT_MATCHER), matcher is optional — presence is allowed and validated for type correctness, absence is also accepted. --- skills/agent-self-evaluation/references/hook-integration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/skills/agent-self-evaluation/references/hook-integration.md b/skills/agent-self-evaluation/references/hook-integration.md index 066556f0..e56455f3 100644 --- a/skills/agent-self-evaluation/references/hook-integration.md +++ b/skills/agent-self-evaluation/references/hook-integration.md @@ -20,7 +20,7 @@ Add this hook to `hooks/hooks.json` to remind the agent to self-evaluate at the } ``` -`Stop` events do not use a `matcher` field. Keep the hook object limited to `hooks` and metadata such as `description`. +`Stop` events do not require a `matcher` field (it is optional for `Stop`, `Notification`, `UserPromptSubmit`, and `SubagentStop` per `scripts/ci/validate-hooks.js`). If omitted, the hook object only needs `hooks` and metadata such as `description`. ## Integration with the Python Evaluator