Skill Detail

Configure project-local behavior rules from operator corrections with Hookify

Turn repeated Claude Code corrections into operator-confirmed local rules, with specific event matchers, warning or blocking actions, and reviewable Markdown configuration.

Developer ToolsClaude Code
Developer Tools Claude Code Security Reviewed
โญ 39.8k GitHub stars
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill configure-project-local-behavior-rules-with-hookify Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
Claude Code; Python 3.7+; Hookify plugin; project-local .claude directory
Install & setup
In Claude Code, run /plugin install hookify@claude-plugins-official using the official marketplace. Ensure Python 3.7+ is available. In the target project invoke /hookify with the behavior to address, confirm the selected patterns and warn/block action, then review the generated .claude/hookify.{rule-name}.local.md files. Use /hookify:list and /hookify:configure to inspect and toggle rules. No installation or invocation was executed during discovery.
Author
Anthropic
Publisher
Organization
Last updated
Oct 16, 2026
Quick brief

Use Hookify in Claude Code when repeated operator corrections need a persistent, project-local rule. Invoke /hookify with a specific unwanted behavior, or without arguments to analyze recent conversation. The workflow identifies candidate patterns, asks the operator which behaviors to address, confirms whether each rule should warn or block, and lets the operator refine the match.

How it works

What this skill actually does

The agent creates reviewable Markdown files at .claude/hookify.{rule-name}.local.md in the current project. YAML frontmatter specifies the name, enabled state, event, pattern or conditions, and optional action. The Markdown body supplies the message shown on a match. Conditions can combine a file path and new text; all conditions must match. Python regular expressions provide the matching syntax.

Invoke this workflow after correcting an unwanted coding habit or when a project needs a targeted reminder. For example, ask /hookify Warn about console.log in TypeScript edits, review the generated file matcher and message, and use harmless sample text to check the pattern. Inspect installed rules with /hookify:list and toggle them with /hookify:configure. Upstream documents that rule edits are read on the next tool use.

The scope is behavior discovery, operator confirmation, local rule generation, and rule maintenance. Bash, file, stop, and prompt events support different checks. A warning permits the operation; a blocking rule can prevent a matching operation or stop completion at the relevant hook. These pattern-based checks need operator review and do not guarantee complete enforcement or prove that tests passed. Claude Code and Python 3.7 or later are required. The documented command and plugin lifecycle make Claude Code the framework mapping.