메뉴
Diagnose Hookify configuration and behavior. Use when the user wants to know why a Hookify rule is not firing, why a hook is loading from the wrong scope, whether Claude and Codex are seeing the same policy, or what gap remains in the current platform surface.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Learn, inspect, and manage Hookify-based hook setups across Claude and Codex. Use when the user mentions Hookify, wants to understand cross-agent hook behavior, wants to inspect current user-level or project-level hook config, or wants help adopting Hookify in a repo or home directory.
Create or update Hookify hook files and rules. Use when the user wants a new Hookify hook, wants to block or warn on a pattern, wants a rule at user or project scope, or wants to express a policy like blocking cmux in `.all`, `.claude`, or `.codex` files.
Migrate existing Claude or Codex hook setups toward Hookify conventions. Use when the user wants to consolidate old hook files, translate existing policies into `.all`, `.claude`, or `.codex` hook files, or reduce duplicated cross-agent hook logic.
| name | hookify-doctor |
| description | Diagnose Hookify configuration and behavior. Use when the user wants to know why a Hookify rule is not firing, why a hook is loading from the wrong scope, whether Claude and Codex are seeing the same policy, or what gap remains in the current platform surface. |
| metadata | {"short-description":"Diagnose Hookify config and behavior"} |
Use this skill when the task is troubleshooting.
Inspect the actual files that should be loading for the target agent and scope. Include symlinks and realpaths.
Check whether the chosen event is one the target agent actually emits, and whether the matcher applies on that event.
Check whether the target agent can really do what the hook is trying to do:
Do not treat parsed-but-unsupported fields as working behavior.
If the platform cannot enforce the requested behavior, say so clearly and name the remaining gap instead of hiding it behind workaround language.
../hookify/references/hook-authoring.md for the shared event subset and asymmetries.../hookify-write-hook/references/event-map.md when the problem might be the wrong event choice.