Create and manage JSON-based event-driven hooks for Claude Code.
npx skills add https://github.com/shishiv/shishiv-resources --skill create-hooks-shishiv
Please help me install this Agent Skill. Skill: create-hooks Source: https://github.com/shishiv/shishiv-resources/tree/main/skills/create-hooks Command: npx skills add https://github.com/shishiv/shishiv-resources --skill create-hooks-shishiv
Claude Code hooks automate repetitive tasks, enforce policies, and inject context without modifying core code. This Skill helps you leverage these powerful event-driven automations to streamline your workflow, ensure safety, and customize Claude's behavior, allowing you to focus on higher-value tasks.
rm -rf), validate user input, or ensure code quality (e.g., auto-format after edits).Bash commands executed by Claude to an audit file, or block git push --force to protect your main branch from accidental overwrites..claude/hooks.json file in your project.PreToolUse hook with a Bash matcher.command hook to log jq -r '.tool_input.command' >> ~/.claude/bash-log.txt.claude --debug.High-intent search queries and answers about installing and using this skill.
Event-driven hooks execute shell commands or LLM prompts in response to events like PreToolUse, PostToolUse, SessionStart, or UserPromptSubmit. Define hooks in `.claude/hooks.json` with tool matchers and command or prompt types to trigger automations without modifying core code.
Yes. Use PreToolUse hooks with Bash tool matchers and validation logic to inspect commands before execution. Configure hooks to block destructive patterns, validate input, or inject safety checks that prevent risky operations from running.
Create a PostToolUse hook with a Bash matcher and command hook that logs output to a file using `jq` to extract tool input. This automatically captures every command Claude runs without manual intervention.
Hooks support both command and prompt types across session events. Use SessionStart or UserPromptSubmit hooks to inject context, trigger desktop notifications, or define custom completion criteria tailored to your workflow.
Hook definitions in `.claude/hooks.json` are read at session start. Test with `claude --debug` to verify your hooks are loaded and firing on the correct events without requiring a full restart between edits.
Hooks require `jq` to parse and extract tool input from JSON events. The `.claude/hooks.json` file must be valid JSON; no additional frameworks or setup beyond a text editor and jq are required to get started.
basher83Generate JSON hook configurations for Claude Code plugin events.
athina-aiExtract Luma event attendees, qualify leads, and export results to Google Sheets.
kvnlooCreate event-driven Claude Code hooks for tool-use monitoring and validation.
meaningfy-wsOrchestrate embedded Python and shell scripts for routine task automation.