Configure

What Configure is

Configure is a slash command published in the athola/claude-night-market repository on GitHub, which has about 339 stars. The repository describes itself as: “23 Claude Code plugins: TDD enforcement hooks, git/PR workflows, spec-driven development, code review, project lifecycle, fix-from-error, maintenance automation, context optimization, research, and multi-LLM delegation. 186 skills, 128 commands, 54 agents.”

A slash command is a reusable prompt saved as a markdown file and run by typing its name after a slash. In Claude Code, custom commands have been merged into skills: a file in .claude/commands/ and a skill folder in .claude/skills/ both create the same kind of command, and existing command files keep working.

Configure gives you a repeatable way to run the same instructions without retyping them, optionally with arguments.

How to install Configure

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/hookify/commands/configure.md, shared under the repository's MIT license. Read the full file on GitHub.

/hookify:configure

Hookify Rules
=============

1. ✅ dangerous-rm (bash, block)
2. ⚠️  warn-console-log (file, warn)
3. ❌ require-tests (stop, warn) [DISABLED]

Select rule number (1-3) or 'q' to quit: 3

Rule: require-tests
Status: Disabled
Event: stop
Action: warn

Actions:
  [e] Enable rule
  [d] Delete rule
  [q] Cancel
…

# Disable a rule
vi .claude/hookify.dangerous-rm.local.md
# Change: enabled: false

# Enable a rule
# Change: enabled: true

Before you install

• Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
• Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
• Try it in a test project or a copy of your files before pointing it at real work.
• Pin the version you tested, and review changes before updating.
• Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ