Nm Hookify Rule Catalog

Browse the rule catalog and guide installation

Security Scan

The skill is an instruction-only catalog that guides installing hookify rules; it requests no credentials and its behavior is consistent with its description, but the runtime instructions assume rule files and installer scripts exist in the user's workspace/repo (they are not bundled), so verify those files before running any install steps.

Purpose & Capability

Name/description match the observed behavior: the SKILL.md lists rules and gives installation guidance. The skill does not request unrelated credentials or binaries.

Instruction Scope

Instructions tell the agent to read rules from skills/rule-catalog/rules/... and to write rule files into .claude/*.local.md and to run python3 plugins/hookify/scripts/install_rule.py. Those file paths and scripts are expected but are not included in the skill bundle — the skill is effectively a pointer to an external repo. The actions (reading/writing local files, running a local Python script) are appropriate for a rule installer, but you should confirm the referenced files/scripts exist and inspect them before executing.

Install Mechanism

There is no install spec (instruction-only), which minimizes direct install risk. However, the SKILL.md references a Python installer script that is not bundled here; if you later run that script from a repository or download it remotely, you should review it first.

Credentials

The skill declares no required env vars, credentials, or privileged config paths. The requested filesystem writes are limited to project/.claude rule files and are proportionate to installing rule templates.

Persistence & Privilege

always:false and normal autonomous invocation are set. The only persistent effect described is writing rule files into .claude; the skill does not request system-wide configuration changes or access to other skills' credentials.

Scan Findings in Context

[no-regex-findings] expected: The scanner found no code files to analyze because this is an instruction-only skill (only SKILL.md is present). The SKILL.md references scripts and rule files that are not bundled; this is expected for a catalog that points at an external repository but means you must verify external files yourself.

Assessment

This skill is essentially documentation and an installer guide — it does not include the rule files or the Python installer it references. Before running any install commands: (1) confirm you have the referenced repository or installer script (plugins/hookify/scripts/install_rule.py) locally, or obtain it from the official upstream URL; (2) inspect any installer script and rule files for unexpected behavior before executing; (3) back up your .claude/ directory or working tree (git status is suggested) so changes can be reverted; (4) avoid running downloaded scripts blindly — prefer manual copy or review-first workflows; and (5) if the agent offers to fetch code from the network on your behalf, ask for the exact source URL and inspect it first.

Night Market Skill — ported from claude-night-market/hookify. For the full experience with agents, hooks, and commands, install the Claude Code plugin.

When To Use

• Browsing available hookify rules by category
• Installing standard pre-built rules into a project
• Looking for ready-made rules before writing custom ones

When NOT To Use

• Writing custom rules from scratch — use hookify:writing-rules instead
• Debugging or modifying existing installed rules
• Converting Python SDK hooks — use hookify:from-hook instead

Table of Contents

• Quick Install
• Available Rules
• git/ - Git Safety
• python/ - Python Quality
• security/ - Security Gates
• workflow/ - Workflow Enforcement
• performance/ - Resource Management
• Installation Instructions
• Method 1: Claude-Assisted (Recommended)
• Method 2: Python Script
• Method 3: Manual Copy
• Rule File Locations
• Customizing Rules
• Creating Pull Requests for New Rules
• Related

Hookify Rule Catalog

Pre-built rules for common scenarios. Install directly or use as templates.

Quick Install

# Install a specific rule
Skill(hookify:rule-catalog) then install git:block-force-push

# Or use the Python installer for bulk operations
python3 plugins/hookify/scripts/install_rule.py git:block-force-push
python3 plugins/hookify/scripts/install_rule.py --category git
python3 plugins/hookify/scripts/install_rule.py --all

Verification: Run python --version to verify Python environment.

Available Rules

git/ - Git Safety

Rule	Action	Default	Description
block-force-push	block	enabled	Prevent force push to main/master
block-destructive-git	block	enabled	Block reset --hard, checkout -- ., clean -fd, etc.
warn-risky-git	warn	enabled	Warn about rebase -i, soft reset, etc.
warn-large-commits	warn	enabled	Warn about large binary files

python/ - Python Quality

Rule	Action	Default	Description
block-dynamic-code	block	enabled	Block dangerous dynamic code execution
warn-print-statements	warn	enabled	Encourage logging over print()

security/ - Security Gates

Rule	Action	Default	Description
require-security-review	block	enabled	Require review for auth code

workflow/ - Workflow Enforcement

Rule	Action	Default	Description
enforce-scope-guard	warn	enabled	Anti-overengineering (imbue)
require-spec-before-code	block	disabled	Spec-first development

performance/ - Resource Management

Rule	Action	Default	Description
warn-large-file-ops	warn	enabled	Watch large file writes

Installation Instructions

Method 1: Claude-Assisted (Recommended)

When you invoke this skill, tell Claude which rule(s) to install:

**Verification:** Run `git status` to confirm working tree state.
Install git:block-force-push

Verification: Run the command with --help flag to verify availability.

Claude will:

1. Read the rule from skills/rule-catalog/rules/git/block-force-push.md
2. Write it to .claude/hookify.block-force-push.local.md
3. Confirm installation

Method 2: Python Script

For bulk operations or automation:

# Install single rule
python3 plugins/hookify/scripts/install_rule.py git:block-force-push

# Install all rules in category
python3 plugins/hookify/scripts/install_rule.py --category python

# Install all rules
python3 plugins/hookify/scripts/install_rule.py --all

# List available rules
python3 plugins/hookify/scripts/install_rule.py --list

# Install to custom directory
python3 plugins/hookify/scripts/install_rule.py git:block-force-push --target /path/to/.claude

Verification: Run the command with --help flag to verify availability.

Method 3: Manual Copy

1. Find rule in plugins/hookify/skills/rule-catalog/rules/<category>/<rule>.md
2. Copy to .claude/hookify.<rule-name>.local.md
3. Edit enabled: true/false as needed

Rule File Locations

Rules are stored relative to this skill:

**Verification:** Run the command with `--help` flag to verify availability.
skills/rule-catalog/
├── SKILL.md (this file)
└── rules/
    ├── git/
    │   ├── block-force-push.md
    │   ├── block-destructive-git.md
    │   ├── warn-risky-git.md
    │   └── warn-large-commits.md
    ├── python/
    │   ├── block-dynamic-code.md
    │   └── warn-print-statements.md
    ├── security/
    │   └── require-security-review.md
    ├── workflow/
    │   ├── enforce-scope-guard.md
    │   └── require-spec-before-code.md
    └── performance/
        └── warn-large-file-ops.md

Verification: Run the command with --help flag to verify availability.

Customizing Rules

After installation, edit the rule in .claude/:

# Change action from warn to block
action: block

# Disable temporarily
enabled: false

# Modify pattern
pattern: your-custom-pattern

Verification: Run the command with --help flag to verify availability.

Creating Pull Requests for New Rules

To add rules to the catalog:

1. Create rule file in appropriate category
2. Follow naming convention: kebab-case.md
3. Include detailed message with alternatives
4. Test thoroughly before submitting
5. Update this SKILL.md catalog table

Related

• Skill(hookify:writing-rules) - Create custom rules
• /hookify:list - Show installed rules
• /hookify:configure - Manage installed rules

Troubleshooting

Common Issues

Command not found Ensure all dependencies are installed and in PATH

Permission errors Check file permissions and run with appropriate privileges

Unexpected behavior Enable verbose logging with --verbose flag