Hooks Manager

Create, edit, configure, and debug hooks for Claude Code, Codex, and Cursor. Use for lifecycle events, command validation, routing shared hooks, notifications, automation, or platform-specific hook configuration.

melvynx d937aa7 14 files · 14.3 KB Updated

File contents

Configure Claude Code, Codex, and Cursor hooks as event-driven commands or prompts. Treat platform syntax as distinct.

  1. Identify the platform and load router.md.
  2. Load the platform file: claude-code.md, codex.md, or cursor.md.
  3. Pick the scope, file path, lifecycle event, and a command hook (deterministic) or prompt hook (reasoning, if supported).
  4. Validate the native config and run the platform smoke check.

Across agents, keep one portable script plus a small adapter per platform. Report unsupported features.

Load as needed: hook-types.md, command-vs-prompt.md, matchers.md, input-output-schemas.md, examples.md, troubleshooting.md.

Check stop_hook_active on Stop/SubagentStop. Use trusted absolute paths, timeouts, and jq validation. Keep blocking rules selective.

melvynx/aiblueprint/tree/main/agents-config/skills/hooks-manager commit d937aa7453

Frequently asked questions

npx skillmds@latest add melvynx/hooks-manager