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). > [!WARNING] > **SECURITY CRITICAL:** > * **Strict JSON**: Printing to `stdout` breaks the CLI. Use `stderr` for logs. > * **Injection Risks**: BASH hooks MUST use `jq`. Never use `grep` on raw input. > * **Dependency Checks**: Scripts MUST fail gracefully (exit 2) if deps like `jq` are missing. ## 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. Instruction Protocol ### Phase 1: Analyze & Clarify 1. **Identify the Event**: Map user intent to the correct Life