hookify

Detect and enforce hookify rules to warn or block risky commands, file edits, and prompts.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ForeverWorld/curdx-ralph --skill hookify-foreverworld
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hookify
Source: https://github.com/ForeverWorld/curdx-ralph/tree/main/skills/hookify
Command: npx skills add https://github.com/ForeverWorld/curdx-ralph --skill hookify-foreverworld

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hookify provides lightweight, repository-local guardrails that detect risky CLI commands, unsafe file edits, and problematic prompts, and then warn or block those actions before they run. It reduces accidental destructive operations, leaked secrets, and unsafe changes by surfacing contextual messages and enforcement at the tool level.

Core Features & Use Cases

  • Define rules as markdown files with YAML frontmatter to match events and patterns and present human-readable messages when rules trigger.
  • Support for single-pattern rules and advanced multi-condition rules that match fields like command, file_path, new_text, and user_prompt using regex and substring operators.
  • Use cases: block dangerous rm commands in CI, warn about console.log in TypeScript commits, require checks before stopping an agent, and prevent accidental edits to .env files.

Quick Start

Add a hookify rule that warns on dangerous rm commands by creating a .claude/hookify.dangerous-rm.local.md file with event set to bash, an appropriate regex pattern, and a clear remediation message.

Frequently Asked Questions about hookify

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

FAQPage Schema
How do I prevent risky CLI commands from running in my repository?▼

You can prevent risky CLI commands by defining hookify rules as markdown files with YAML frontmatter to match bash events and block dangerous operations before they execute. Rules use regex patterns to detect commands and present contextual warning messages.

Can I block unsafe file edits to specific paths like .env files?▼

Yes, you can block unsafe file edits by creating hookify rules that target file edit events and match specific file paths like .env using regex or substring operators. The rule triggers a warning or blocks the edit action before it applies.

What are multi-condition rules for monitoring developer safety guardrails?▼

Multi-condition rules match multiple fields like command, file_path, new_text, and user_prompt simultaneously using regex and substring operators. They enable complex automated guardrails that evaluate several aspects of a single event before triggering warnings or blocking actions.

How do I set up a hookify rule to warn about dangerous rm commands?▼

Create a .claude/hookify.dangerous-rm.local.md file with YAML frontmatter setting the event to bash, define an appropriate regex pattern for rm commands, and write a clear remediation message in the body to warn users when the pattern matches.

Does hookify work with agent stop checks and user prompt monitoring?▼

Yes, hookify applies to agent stop checks and user prompt monitoring by defining rules with the appropriate event type in the YAML frontmatter. It evaluates prompts and stop actions against regex patterns to enforce automated guardrails for developer safety.

What limitations should I expect when using regex rules for command blocking?▼

Regex rules for command blocking require precise pattern matching to avoid false positives and depend on the event types supported by the plugin workflow, including bash commands, file edits, agent stops, and user prompts, limiting scope to these monitored events.