Hookify Help

Hookify Plugin Help

Present the hookify plugin to the user: architecture, rule format, available skills, and getting started steps.

Overview

Hookify creates custom hooks that prevent unwanted behaviors via simple markdown configuration files instead of editing hooks.json.

How It Works

1. Hook System

Hookify installs generic hooks that run on these events:

• preToolUse: Before any tool executes (powershell, edit, create, etc.)
• postToolUse: After a tool executes
• agentStop: When Copilot wants to stop working
• userPromptSubmitted: When user submits a prompt

These hooks read configuration files from .github/hookify.*.local.md and check if any rules match the current operation.

2. Configuration Files

Users create rules in .github/hookify.{rule-name}.local.md files:

---
name: warn-dangerous-rm
enabled: true
event: bash
pattern: rm\s+-rf
---

⚠️ **Dangerous rm command detected!**

This command could delete important files. Please verify the path.

Key fields:

• name: Unique identifier for the rule
• enabled: true/false to activate/deactivate
• event: bash, file, stop, prompt, or all
• pattern: Regex pattern to match

The message body is what Copilot sees when the rule triggers.

3. Creating Rules

Option A: Use hookify-create skill

hookify-create Don't use console.log in production files

This analyzes your request and creates the appropriate rule file.

Option B: Create manually Create .github/hookify.my-rule.local.md with the format above.

Option C: Analyze conversation

hookify-create

Without arguments, hookify analyzes recent conversation to find behaviors you want to prevent.

Available Skills

• hookify-create - Create hooks from conversation analysis or explicit instructions
• hookify-help - Show this help (what you're reading now)
• hookify-list - List all configured hooks
• hookify-configure - Enable/disable existing hooks interactively