mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-04-03 07:33:31 +08:00
4813ed753f
Ports functionality from 10+ separate plugins into ECC so users only need one plugin installed. Consolidates: pr-review-toolkit, feature-dev, commit-commands, hookify, code-simplifier, security-guidance, frontend-design, explanatory-output-style, and personal skills. New agents (8): code-architect, code-explorer, code-simplifier, comment-analyzer, conversation-analyzer, pr-test-analyzer, silent-failure-hunter, type-design-analyzer New commands (9): commit, commit-push-pr, clean-gone, review-pr, feature-dev, hookify, hookify-list, hookify-configure, hookify-help New skills (8): frontend-design, hookify-rules, github-ops, knowledge-ops, lead-intelligence, oura-health, pmx-guidelines, remotion Enhanced skills (8): article-writing, content-engine, market-research, investor-materials, investor-outreach, x-api, security-scan, autonomous-loops — merged with personal skill content New hook: security-reminder.py (pattern-based OWASP vulnerability warnings on file edits) Totals: 36 agents, 69 commands, 128 skills, 29 hook scripts
1.3 KiB
1.3 KiB
description
| description |
|---|
| Create hooks to prevent unwanted behaviors from conversation analysis or explicit instructions |
Create hook rules to prevent unwanted Claude Code behaviors by analyzing conversation patterns or explicit user instructions.
Usage
/hookify [description of behavior to prevent]
If no arguments provided, analyze the current conversation to find behaviors worth preventing.
Workflow
Step 1: Gather Behavior Info
- With arguments: Parse the user's description of the unwanted behavior
- Without arguments: Use the conversation-analyzer agent to find:
- Explicit corrections ("no, don't do that", "stop doing X")
- Frustrated reactions to repeated mistakes
- Reverted changes
- Repeated similar issues
Step 2: Present Findings
Show the user what behaviors were identified and proposed hook rules:
- Behavior description
- Proposed event type (bash/file/stop/prompt/all)
- Proposed pattern/matcher
- Proposed action (block/warn)
Step 3: Generate Rule Files
For each approved rule, create a file at .claude/hookify.{name}.local.md:
---
name: rule-name
enabled: true
event: bash|file|stop|prompt|all
action: block|warn
pattern: "regex pattern"
---
Message shown when rule triggers.
Step 4: Confirm
Report created rules and how to manage them (/hookify-list, /hookify-configure).