← ClaudeAtlas

hook-developmentlisted

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.
nerymurillohnd/the-claude-factory · ★ 1 · AI & Automation · score 67
Install: claude install-skill nerymurillohnd/the-claude-factory
# Claude Code hooks A hook runs only when three levels line up: the **event** fires, a **matcher group** matches, and the **handler** (with its optional `if`) is allowed to start. Most "my hook never runs" bugs sit in one of these levels, not in the script. A hook's effect is decided by three things together: its **exit code**, the **shape of its stdout**, and the **event** it runs on. This file holds the workflows, the routing and the rules that cut across them; the references hold the detail. ## Sources and freshness Source of truth: the official pages, starting at [Hook lifecycle](https://code.claude.com/docs/en/hooks#hook-lifecycle), [Configuration](https://code.claude.com/docs/en/hooks#configuration) and [Hook input and output](https://code.claude.com/docs/en/hooks#hook-input-and-output). The references here **condense** those pages; they are not complete. Every section that states hook facts carries a `Docs:` line with the exact official URL, and [docs-map.md](references/docs-map.md) lists every official heading in scope with its URL and how to open it. - Before a rule decides a design, a fix or a review finding, open its official section and read it in full. Use the references to find the section, not instead of it. - Cite the URL with the anchor for every rule you state. - Get `claude --version` before relying on a version-gated behavior and check it against [sources.md](references/sources.md). Hooks change most releases, and the docs describe the latest release,