debug-hooks
FeaturedSystematic hook debugging workflow. Use when hooks aren't firing, producing wrong output, or behaving unexpectedly.
Install
Quality Score: 94/100
Skill Content
Details
- Author
- vibeeval
- Repository
- vibeeval/vibecosystem
- Created
- 8 months ago
- Last Updated
- 6 days ago
- Language
- C#
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
debug-hooks
Systematic hook debugging workflow. Use when hooks aren't firing, producing wrong output, or behaving unexpectedly.
hook-development
Use for auditing, reviewing or debugging Claude Code hooks, and for questions about how they behave - a hook that never fires, fires on the wrong calls, or has its block, deny, allow, exit code 2 or additionalContext ignored; a check of the hooks in settings.json, hooks/hooks.json or skill and agent frontmatter before a release; the debug log; or how an event, matcher, if filter, handler type, exit code, JSON output, timeout or async hook works. Covers command, HTTP, MCP tool, prompt and agent hooks, workspace trust and mods in the same chain, checked against the current docs and the changelog for the installed version, with a config linter, a hook probe and a changelog script. Use it even when the user only pastes a hook or says it does nothing. Not for writing a new hook (writing-hooks), Git hooks, React hooks or webhooks.
hooks-configuration
Claude Code hooks creation and debugging assistant. Configures PreToolUse, PostToolUse, Stop, SessionStart, UserPromptSubmit, and other lifecycle hooks in settings.json. Creates command hooks (Bash/Python scripts), prompt-based hooks (LLM evaluation), and agent hooks. Handles exit codes (0=allow, 1=error, 2=deny), matchers, async execution, and security enforcement patterns. Use when creating a hook, debugging a hook, blocking dangerous commands, auto-formatting on save, running tests on stop, or adding session logging.