Skip to main content
command official · Anthropic

configure — Claude Code command: toggle hookify rules

Lists your hookify rules and lets you flip them on or off one by one. Handy once the rule set grows and some of it gets in the way.

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin install hookify@claude-plugins-official
Open on GitHub

What configure does

The configure command ships with the hookify plugin. It globs .claude/hookify.*.local.md, pulls name and enabled out of each file's frontmatter, and builds a list showing where every rule stands right now. You then pick which ones to flip through an AskUserQuestion prompt.

Toggling is a plain edit of those same files: enabled: false becomes enabled: true and the other way round, with quoted values handled too. When it finishes, the command prints what got enabled, what got disabled and what stayed put. No restart is involved — the new state applies the next time a tool runs.

It loads the hookify:writing-rules skill first so it knows the rule format. With no rule files present, it points you at /hookify to create one. Deleting a rule is out of scope here; remove its .local.md by hand if you want it gone.

What it helps with

  • silence a rule that fires far too often
  • bring back a rule you disabled weeks ago
  • see which hookify rules exist and whether each is on
  • flip several rules in one pass instead of editing files yourself

Example prompts for the agent

  • List my hookify rules and let me turn some off
  • Disable warn-console-log, leave the rest alone
  • Turn warn-dangerous-rm back on

How to install configure

1Plugin marketplace

/plugin install hookify@claude-plugins-official

2Manually: put the files in place

.claude/commands/configure.md

Call it with /configure. For all projects use ~/.claude/commands/

Questions about configure

How do I install configure in Claude Code?

From the marketplace: run /plugin marketplace add anthropics/claude-plugins-official, then /plugin install hookify@claude-plugins-official. The command file lands at .claude/commands/configure.md.

What does the configure command do?

It finds every hookify rule file, reports the current state of each, and flips the enabled field on the ones you select.

Do I need to restart Claude after toggling rules?

No. The change takes effect immediately, on the next tool use.

Source text

configure.md · Apache-2.0
---
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:

```json
{
  "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

© Anthropic · Apache-2.0 · anthropics/claude-plugins-official

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

From the same set145

The whole set →

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor