메뉴
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.
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.
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.
| name | hookify-migrate |
| description | 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. |
| metadata | {"short-description":"Migrate hooks into Hookify"} |
Use this skill when the task is to move an existing hook setup toward Hookify conventions.
.all, .claude, and .codex placements.Inspect:
.hookify/ treesSeparate current behavior into:
Do not rewrite semantics just to make the tree look tidy. The goal is a faithful migration first.
After grouping:
.all.claude.codex../hookify/references/setup-surfaces.md for where current hook config can live.../hookify/references/hook-authoring.md for the shared event subset and important asymmetries.