fraujulian/MyAiConfiguration
1
0
Fork 0
Code Issues Pull Requests Actions Activity

docs(hooks): clarify which hook scripts are actually registered

Browse Source 
Only the Stop hook (flashbang) is wired into the generated client
configuration. Validate-CommandSafety and Invoke-PostChangeVerification
are utility scripts nothing here invokes automatically; the previous
wording could be read as implying otherwise.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
Julian lechner
2026-09-11 15:44:09 +02:00
co-authored by Claude Sonnet 5
parent 077eaa55be
commit 1abb3a2d32
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
shared/hooks/README.md
+2
View File
@@ -1,3 +1,5 @@
# Hooks # Hooks
Hooks are conservative entry points shared by clients. They validate obvious command hazards, check repository-local configuration inputs, and provide an optional post-change verification command. They do not bypass client permission prompts or grant access. Hooks are conservative entry points shared by clients. They validate obvious command hazards, check repository-local configuration inputs, and provide an optional post-change verification command. They do not bypass client permission prompts or grant access.
Only the `Stop` hook (`flashbang`) is registered in the generated client configuration. `Validate-CommandSafety`/`validate-command-safety.sh` and `Invoke-PostChangeVerification`/`invoke-post-change-verification.sh` are utility scripts, not active hooks; nothing in this repository invokes them automatically. Wire one up as a client-native `PreToolUse`/equivalent hook yourself if you want it enforced, and do not assume it runs otherwise.