hookify-rules

Define and enforce custom code safety rules with hookify conditions.

Updated Jun 22, 2026

Search Tags:#code review #security #code safety #rule management #hookify

Ready to run

npx skills add https://github.com/hector-manny/bussbot --skill hookify-rules-hector-manny

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: hookify-rules
Source: https://github.com/hector-manny/bussbot/tree/main/.cursor/skills/hookify-rules
Command: npx skills add https://github.com/hector-manny/bussbot --skill hookify-rules-hector-manny

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining code safety by enabling users to create, configure, and manage hookify rules, which help prevent potential security risks and coding mistakes.

Core Features & Use Cases

Rule Creation: Users can define custom rules to trigger warnings or block actions based on specific patterns or conditions.
Event-Based Rules: Rules can be triggered on various events such as file changes, bash commands, or prompts.
Conditional Logic: Implement complex rules with multiple conditions that must all match for the rule to trigger.
Use Case: For instance, a developer might create a rule to warn when an API key is added to a .env file, ensuring that sensitive information remains secure.

Quick Start

To create a new hookify rule, use the /hookify [description] command. For example, /hookify Prevent accidental API key exposure.

Frequently Asked Questions about hookify-rules

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

FAQPage Schema

How do I prevent API key exposure in .env files during code review?▼

To prevent API key exposure during code review, you can create custom hookify rules that trigger warnings or block actions when sensitive patterns are detected in files like .env. This enforces code safety by preventing security vulnerabilities before they reach the repository.

How do I create custom code safety rules for development environments?▼

You create custom code safety rules by using the /hookify command followed by a description, such as /hookify Prevent accidental API key exposure. The hookify engine then executes these rules based on file changes, bash commands, or prompts to enforce your specific conditions.

Can I trigger code safety checks on bash commands and file changes?▼

Yes, you can trigger code safety checks on bash commands, file changes, and prompts. By configuring event-based hookify rules, the engine monitors these specific events and evaluates conditional logic to block actions or warn developers of coding errors.

Does hookify support conditional logic for complex code review rules?▼

Hookify supports conditional logic for complex code review rules by allowing multiple conditions to be defined. All specified conditions must match for the rule to trigger, enabling precise enforcement of code safety patterns during development.

Do I need a specific engine to run hookify rules for security vulnerabilities?▼

Yes, you need the hookify engine to execute rules for security vulnerabilities. The engine processes your custom patterns and conditions, applying them to file and command triggers to actively prevent common coding mistakes during the development process.