help

Document Hookify plugin operation and rule configuration for Claude governance.

15|6|Updated May 7, 2026
One-click install
npx skills add https://github.com/MinhThang1009/dotclaude --skill help-minhthang1009
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: help
Source: https://github.com/MinhThang1009/dotclaude/tree/main/plugins/hookify/skills/help
Command: npx skills add https://github.com/MinhThang1009/dotclaude --skill help-minhthang1009

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hookify helps teams implement safety and governance in Claude workflows by letting users define lightweight, markdown-based rules instead of editing JSON configuration files, enabling immediate, rule-based behavior control.

Core Features & Use Cases

  • PreToolUse, PostToolUse, Stop, and UserPromptSubmit hooks automate guardrails around tool usage.
  • Configuration files at .claude/hookify.{rule-name}.local.md define name, enabled, event, and pattern to block or warn.
  • Create and manage rules easily with the /hookify command or manual rule files for quick governance and safety checks.

Quick Start

Create a hook rule with /hookify to warn when a dangerous command like rm -rf is entered.

Frequently Asked Questions about help

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Claude behavior rules without editing JSON files?▼

You can configure Claude behavior rules by creating lightweight markdown files at .claude/hookify.{rule-name}.local.md, defining frontmatter for name, enabled, event, and pattern to block or warn.

What Hookify events can I use to automate guardrails for tool usage?▼

Hookify supports PreToolUse, PostToolUse, Stop, and UserPromptSubmit events to automate guardrails and enforce safety checks around tool usage in Claude workflows.

How do I create a Hookify rule to warn when dangerous commands are entered?▼

Use the /hookify command to quickly create a hook rule that warns users when dangerous commands like rm -rf are entered, enabling immediate rule-based behavior control.

What frontmatter structure is required for Hookify rule configuration files?▼

Hookify rule configuration files require frontmatter structure defining name, enabled, event, and pattern fields to properly govern Claude behavior through immediate rule loading.

Can I manage Hookify rules manually instead of using the /hookify command?▼

Yes, you can manually create and manage rule files at .claude/hookify.{rule-name}.local.md for quick governance and safety checks without using the /hookify command.

Does Hookify support immediate rule loading for Claude workflow automation?▼

Yes, Hookify supports immediate rule loading from markdown-based configuration files, enabling instant behavior control and safety governance without restarting or reconfiguring.