From hookify
Lists all configured hookify rules in the project by scanning .claude/hookify.*.local.md files and displaying their frontmatter, status, and message previews in a table.
How this command is triggered — by the user, by Claude, or both
Slash command
/hookify:listThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# List Hookify Rules **Load hookify:writing-rules skill first** to understand rule format. Show all configured hookify rules in the project. ## Steps 1. Use Glob tool to find all hookify rule files: 2. For each file found: - Use Read tool to read the file - Extract frontmatter fields: name, enabled, event, pattern - Extract message preview (first 100 chars) 3. Present results in a table: 4. For each rule, show a brief preview: 5. Add helpful footer: ## If No Rules Found If no hookify rules exist: /hookify Warn me when I use console.log
Load hookify:writing-rules skill first to understand rule format.
Show all configured hookify rules in the project.
Use Glob tool to find all hookify rule files:
pattern: ".claude/hookify.*.local.md"
For each file found:
Present results in a table:
## Configured Hookify Rules
| Name | Enabled | Event | Pattern | File |
|------|---------|-------|---------|------|
| warn-dangerous-rm | ✅ Yes | bash | rm\s+-rf | hookify.dangerous-rm.local.md |
| warn-console-log | ✅ Yes | file | console\.log\( | hookify.console-log.local.md |
| check-tests | ❌ No | stop | .* | hookify.require-tests.local.md |
**Total**: 3 rules (2 enabled, 1 disabled)
### warn-dangerous-rm
**Event**: bash
**Pattern**: `rm\s+-rf`
**Message**: "⚠️ **Dangerous rm command detected!** This command could delete..."
**Status**: ✅ Active
**File**: .claude/hookify.dangerous-rm.local.md
---
To modify a rule: Edit the .local.md file directly
To disable a rule: Set `enabled: false` in frontmatter
To enable a rule: Set `enabled: true` in frontmatter
To delete a rule: Remove the .local.md file
To create a rule: Use `/hookify` command
**Remember**: Changes take effect immediately - no restart needed
If no hookify rules exist:
## No Hookify Rules Configured
You haven't created any hookify rules yet.
To get started:
1. Use `/hookify` to analyze conversation and create rules
2. Or manually create `.claude/hookify.my-rule.local.md` files
3. See `/hookify:help` for documentation
Example:
/hookify Warn me when I use console.log
Check `${CLAUDE_PLUGIN_ROOT}/examples/` for example rule files.
npx claudepluginhub p/ilindsley-hookify-plugins-hookify59plugins reuse this command
First indexed Dec 31, 2025
Showing the 6 earliest of 59 plugins
/listLists all configured hookify rules in the project by scanning .claude/hookify.*.local.md files and displaying their frontmatter, status, and message previews in a table.
/hookify-listLists all configured hookify rules in a formatted table with name, enabled state, event, pattern, and file path. Also displays rule count and reminds how to modify rules.
/hookify-listLists all configured hookify rules in a formatted table showing name, enabled status, event, action, pattern, and file path.
/listLists all installed and generated CLI-Anything tools with version, status, and path. Supports custom scan directories and JSON output.
/listLists beads project issues with rich filtering by status, priority, type, assignee, labels, title, date ranges, and more. Outputs as table, JSON, or graph formats.
/listLists all stored learnings with optional sorting by recency or usefulness, and filtering by category or project.