Hookify: Create Claude Code Hooks from Plain Markdown Rules

Hookify is an Anthropic plugin that lets you create Claude Code hooks without editing hooks.json. You describe the behavior you want to prevent, and Hookify writes a small Markdown rule file with a regex pattern and the message Claude sees when the pattern matches.

Checked 24 Oct 2026 against the plugin’s README, plugin.json and marketplace.json.

Who it is for

Developers who keep correcting the same Claude behavior, such as risky shell commands or leftover debug code, and want a guardrail without writing hook scripts.

Install

/plugin install hookify@claude-plugins-official

Create a rule from an instruction:

/hookify Warn me when I use rm -rf commands

Run /hookify with no arguments to have it analyze the recent conversation for behaviors you corrected.

What it does

• Writes rules to .claude/hookify.<name>.local.md in your project.
• Supports events bash, file, stop, prompt and all.
• Each rule has an action of warn (default) or block.
• Advanced rules combine conditions on fields like command, file_path or new_text, using operators such as regex_match, contains and not_contains.
• Helper commands: /hookify:list, /hookify:configure to enable or disable rules, and /hookify:help.

Use cases

• Block rm -rf and other destructive commands.
• Warn when console.log( or debugger; lands in a file.
• Stop Claude from ending a turn if no test command appears in the transcript.

Pros

• Plain Markdown rules you can read, edit and commit.
• No restart needed after changes.
• A gentle entry point to hooks before writing your own.

Cons and caveats

• Regex rules are easy to get too broad or too narrow; test patterns first.
• Many active rules, or rules on all events, can slow tool calls.
• The README says MIT while the plugin folder ships an Apache 2.0 LICENSE file.

Links

• Plugin folder: plugins/hookify
• Related: hooks guide, Plugin Dev, Claude Plugins Official