Files

T

Julian lechnerandClaude Sonnet 5 1163f6d96e fix: mark shell scripts executable in git

All tracked .sh files were stored as mode 100644 (non-executable), even
though the CI workflow and normal usage invoke several of them directly
(./scripts/build.sh) rather than through `bash`. On a fresh Linux
checkout this fails with a permission error.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-09-11 16:06:37 +02:00

scripts

fix: mark shell scripts executable in git

2026-09-11 16:06:37 +02:00

flashbang.ps1

feat(hooks): add cross-platform safety and status hooks

2026-09-11 14:42:57 +02:00

flashbang.sh

fix: mark shell scripts executable in git

2026-09-11 16:06:37 +02:00

README.md

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

2026-09-11 15:44:09 +02:00

README.md

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.

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.