hooks-creatorlisted

# Hooks Creator **Purpose**: Create robust, secure, and compliant Gemini CLI hooks that intercept and customize the agent's lifecycle (e.g., blocking tools, injecting context, logging). ## 1. Red Flags (Anti-Rationalization) **STOP and READ THIS if you are thinking:** - "I'll use `grep` to parse JSON in Bash because it's faster" -> **WRONG**. This is a security vulnerability. You **MUST** use `jq`. - "I'll just print a debug message to stdout" -> **WRONG**. This breaks JSON parsing. **ALL** logs must go to `stderr`. - "I can skip the dependency check" -> **WRONG**. Scripts will fail silently. functionality. Always check for `jq` or node modules. - "I'll use `exit 1` for a denial" -> **WRONG**. Use `exit 0` with `{"decision": "deny"}` for structured feedback, or `exit 2` for system errors. ## 2. Capabilities - Generate **Bash** hooks for simple logic (using `jq`). - Generate **Node.js** hooks for complex logic or heavy JSON processing. - Configure `settings.json` with correct matchers and event types. - Validate security and performance best practices. ## 3. Execution Mode - **Mode**: `prompt-first` - **Why this mode**: the skill ships no `scripts/` of its own — it authors hook scripts for the user's project. Choosing the event, the language (Bash vs Node.js) and the matcher is judgement over the request plus `references/`; the deterministic work lives in the generated hook, not here. - **Script Contract**: none of its own. The contract the *generated* hook must meet is §5