hooks-edit

Temporarily bypass constitutional hooks via /hooks-edit with explicit deactivation and CONSTITUTIONAL_HOOKS_BYPASS.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/EndUser123/cc-skills-utils --skill hooks-edit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hooks-edit
Source: https://github.com/EndUser123/cc-skills-utils/tree/main/skills/hooks-edit
Command: npx skills add https://github.com/EndUser123/cc-skills-utils --skill hooks-edit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Editing Claude Code hooks can cause self-blocking and enforcement to prevent changes, making edits risky. This skill provides a safe bypass to allow edits without breaking the hook system.

Core Features & Use Cases

  • Temporary bypass of constitutional hooks during editing to prevent self-blocking.
  • Explicit activation and deactivation to avoid leaving hooks bypassed.
  • Context-aware safeguards and integration with git-safety workflows for secure editing.
  • Compatibility with standard compliance checks (standards, compliance) to ensure validations.

Quick Start

Invoke /hooks-edit to suspend hooks, and run /hooks-edit --off to re-enable them.

Frequently Asked Questions about hooks-edit

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

FAQPage Schema
Why do Claude Code hooks block edits and how can I safely bypass them?▼

Constitutional hooks enforce safety by preventing changes, but you can bypass hooks temporarily using an explicit activation command. This suspension integrates with git-safety workflows and requires manual deactivation after editing to restore enforcement.

How do I activate and deactivate the hook bypass for editing sessions?▼

Activate the bypass by invoking the explicit edit command to suspend hooks, make your changes, then run the deactivation command with the off flag to re-enable enforcement. Explicit deactivation ensures constitutional hooks are restored after editing.

Does the hook bypass work with git-safety workflows and compliance checks?▼

The hook bypass integrates with git-safety workflows to provide secure editing context and maintains compatibility with standard compliance checks. This ensures validations run correctly while constitutional hooks are temporarily suspended.

What happens if I forget to re-enable constitutional hooks after editing?▼

Leaving hooks bypassed disables enforcement and self-blocking protections indefinitely. The skill requires explicit deactivation after editing to ensure constitutional hooks are re-enabled and safety enforcement is restored.

When should I use a temporary hook bypass instead of permanently disabling hooks?▼

Use a temporary bypass when you need to edit hooks without breaking the enforcement system, as it requires explicit deactivation afterward. This keeps safety intact long-term, unlike permanent disabling which removes enforcement entirely.