configure

Toggle hookify rules by editing YAML frontmatter in .claude/hookify.*.local.md files.

15|6|Updated May 7, 2026
One-click install
npx skills add https://github.com/MinhThang1009/dotclaude --skill configure-minhthang1009
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: configure
Source: https://github.com/MinhThang1009/dotclaude/tree/main/plugins/hookify/skills/configure
Command: npx skills add https://github.com/MinhThang1009/dotclaude --skill configure-minhthang1009

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to quickly enable or disable individual hookify rules and adjust their behavior from a single, interactive interface.

Core Features & Use Cases

  • Interactive rule toggling: scans existing .claude/hookify.*.local.md rule files, presenting their current enabled state.
  • Safe updates: edits the enablement flag in rule frontmatter and applies changes immediately for the next tool use.
  • Use Case: a developer temporarily disables a noisy rule in a feature branch while maintaining it in the main branch.

Quick Start

Ask me to enable or disable a specific hookify rule and confirm the updated state.

Frequently Asked Questions about configure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I toggle hookify rule states interactively in a local development environment?

To toggle hookify rule states interactively, the skill reads existing .claude/hookify.*.local.md files, presents their current enabled state, and safely edits the YAML frontmatter to apply changes immediately for the next tool use.

Can I temporarily disable a specific hookify rule for a feature branch without removing the file?

Yes, you can temporarily disable a specific hookify rule by toggling the enablement flag in the rule's YAML frontmatter, maintaining the file in your branch while adjusting behavior immediately.

What is the safest way to edit YAML frontmatter in hookify rule files?

The safest way to edit YAML frontmatter in hookify rule files is through atomic updates that modify only the enablement flag, ensuring the new state takes effect on the next tool use without corrupting the file structure.

Does the hookify configuration skill work in both local development and CI environments?

Yes, the hookify configuration skill applies changes in both local development environments and CI pipelines where hookify rules govern behavior, ensuring consistent rule enablement across workflows.

Why does my updated hookify rule not take effect immediately after editing the markdown file?

If your updated hookify rule does not take effect immediately, ensure the YAML frontmatter was edited atomically and safely, as the new state only applies on the next tool use after a proper toggle.

Do I need any dependencies to manage hookify rules interactively?

No external dependencies are required to manage hookify rules interactively; the skill operates by scanning existing .claude/hookify.*.local.md files and editing their YAML frontmatter directly.