/configure
Enable or disable hookify rules interactively
> /plugin marketplace add LING71671/Open-ClaudeCodeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/configure
Context preview
What this command does when you run it.
Enable or disable hookify rules interactively
Command definition
configure.mddescription: Enable or disable hookify rules interactively
allowed-tools: ["Glob", "Read", "Edit", "AskUserQuestion", "Skill"]
Configure Hookify Rules
**Load hookify:writing-rules skill first** to understand rule format.
Enable or disable existing hookify rules using an interactive interface.
Steps
1. Find Existing Rules
Use Glob tool to find all hookify rule files:
pattern: ".claude/hookify.*.local.md"
If no rules found, inform user:
No hookify rules configured yet. Use `/hookify` to create your first rule.
2. Read Current State
For each rule file:
- Read the file
- Extract `name` and `enabled` fields from frontmatter
- Build list of rules with current state
3. Ask User Which Rules to Toggle
Use AskUserQuestion to let user select rules:
{
"questions": [
{
"question": "Which rules would you like to enable or disable?",
"header": "Configure",
"multiSelect": true,
"options": [
{
"label": "warn-dangerous-rm (currently enabled)",
"description": "Warns about rm -rf commands"
},
{
"label": "warn-console-log (currently disabled)",
"description": "Warns about console.log in code"
},
{
"label": "require-tests (currently enabled)",
"description": "Requires tests before stopping"
}
]
}
]
}**Option format:**
- Label: `{rule-name} (currently {enabled|disabled})`
- Description: Brief description from rule's message or pattern
4. Parse User Selection
For each selected rule:
- Determine current state from label (enabled/disabled)
- Toggle state: enabled → disabled, disabled → enabled
5. Update Rule Files
For each rule to toggle:
- Use Read tool to read current content
- Use Edit tool to change `enabled: true` to `enabled: false` (or vice versa)
- Handle both with and without quotes
**Edit pattern for enabling:**
old_string: "enabled: false"
new_string: "enabled: true"
**Edit pattern for disabling:**
old_string: "enabled: true"
new_string: "enabled: false"
6. Confirm Changes
Show user what was changed:
## Hookify Rules Updated
**Enabled:**
- warn-console-log
**Disabled:**
- warn-dangerous-rm
**Unchanged:**
- require-tests
Changes apply immediately - no restart needed
Important Notes
- Changes take effect immediately on next tool use
- You can also manually edit .claude/hookify.*.local.md files
- To permanently remove a rule, delete its .local.md file
- Use `/hookify:list` to see all configured rules
Edge Cases
**No rules to configure:**
- Show message about using `/hookify` to create rules first
**User selects no rules:**
- Inform that no changes were made
**File read/write errors:**
- Inform user of specific error
- Suggest manual editing as fallback
Read more
description: Enable or disable hookify rules interactively allowed-tools: ["Glob", "Read", "Edit", "AskUserQuestion", "Skill"]
Configure Hookify Rules
**Load hookify:writing-rules skill first** to understand rule format.
Enable or disable existing hookify rules using an interactive interface.
Steps
1. Find Existing Rules
Use Glob tool to find all hookify rule files:
pattern: ".claude/hookify.*.local.md"
If no rules found, inform user:
No hookify rules configured yet. Use `/hookify` to create your first rule.
2. Read Current State
For each rule file:
- Read the file
- Extract `name` and `enabled` fields from frontmatter
- Build list of rules with current state
3. Ask User Which Rules to Toggle
Use AskUserQuestion to let user select rules:
{
"questions": [
{
"question": "Which rules would you like to enable or disable?",
"header": "Configure",
"multiSelect": true,
"options": [
{
"label": "warn-dangerous-rm (currently enabled)",
"description": "Warns about rm -rf commands"
},
{
"label": "warn-console-log (currently disabled)",
"description": "Warns about console.log in code"
},
{
"label": "require-tests (currently enabled)",
"description": "Requires tests before stopping"
}
]
}
]
}**Option format:**
- Label: `{rule-name} (currently {enabled|disabled})`
- Description: Brief description from rule's message or pattern
4. Parse User Selection
For each selected rule:
- Determine current state from label (enabled/disabled)
- Toggle state: enabled → disabled, disabled → enabled
5. Update Rule Files
For each rule to toggle:
- Use Read tool to read current content
- Use Edit tool to change `enabled: true` to `enabled: false` (or vice versa)
- Handle both with and without quotes
**Edit pattern for enabling:**
old_string: "enabled: false" new_string: "enabled: true"
**Edit pattern for disabling:**
old_string: "enabled: true" new_string: "enabled: false"
6. Confirm Changes
Show user what was changed:
## Hookify Rules Updated **Enabled:** - warn-console-log **Disabled:** - warn-dangerous-rm **Unchanged:** - require-tests Changes apply immediately - no restart needed
Important Notes
- Changes take effect immediately on next tool use
- You can also manually edit .claude/hookify.*.local.md files
- To permanently remove a rule, delete its .local.md file
- Use `/hookify:list` to see all configured rules
Edge Cases
**No rules to configure:**
- Show message about using `/hookify` to create rules first
**User selects no rules:**
- Inform that no changes were made
**File read/write errors:**
- Inform user of specific error
- Suggest manual editing as fallback
完整开源的 Claude Code 项目 - 基于 Anthropic 官方源码重建 🌐 Languages: 中文 | English
Repo: LING71671/Open-ClaudeCode
Other commands on open-claudecode.
- /new-sdk-app
Create and setup a new Claude Agent SDK application
Open command - /code-review
Code review a pull request
Open command - /clean_gone
Cleans up all git branches marked as [gone] (branches that have been deleted on the remote but still exist locally), including removing associated worktrees.
Open command - /commit-push-pr
Commit, push, and open a PR
Open command - /commit
Create a git commit
Open command - /feature-dev
Guided feature development with codebase understanding and architecture focus
Open command

