hooks-disable

Disable or bypass yka-code hooks for persistent or single-execution control.

Updated Apr 13, 2026

Search Tags:#system configuration #hook management #yka-code #disabling hooks #single-command bypass

Ready to run

npx skills add https://github.com/youssefKadaouiAbbassi/yka-code --skill hooks-disable

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: hooks-disable
Source: https://github.com/youssefKadaouiAbbassi/yka-code/tree/main/skills/hooks-disable
Command: npx skills add https://github.com/youssefKadaouiAbbassi/yka-code --skill hooks-disable

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill allows users to disable specific yka-code hooks or all hooks at once, providing control over the execution of hooks in the yka-code environment.

Core Features & Use Cases

Persistent Disabling: Disable a hook so it does not run on subsequent executions.
Single-Command Bypass: Temporarily bypass a hook for a single command execution.
Use Case: If you want to skip a pre-push hook for a particular commit, you can use this Skill to disable it for that one instance.

Quick Start

To disable the 'pre-pr-gate' hook, run: /hooks-disable pre-pr-gate

Frequently Asked Questions about hooks-disable

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

FAQPage Schema

How do I disable yka-code hooks for a single command execution?▼

To disable yka-code hooks for a single command, you can use a single-command bypass. This temporarily skips hook execution for one instance, such as skipping a pre-push hook for a specific commit, without affecting future runs.

Can I persistently disable a specific hook in the yka-code environment?▼

Yes, you can persistently disable specific yka-code hooks. This prevents the targeted hook from running on subsequent executions, providing ongoing control over your system configuration and hook management processes.

What is the best way to bypass a pre-push hook for one commit?▼

The best way to bypass a pre-push hook for one commit is using a single-command bypass. This approach temporarily disables the hook for that specific execution, allowing the command to proceed without triggering the hook.

Do I need yka-code-setup to modify system configuration for hook management?▼

Yes, you need access to yka-code-setup to modify system configuration for hook management. This access is required to properly disable or bypass hooks within the yka-code environment at the system level.

Why would I need to disable system-level hooks in yka-code environments?▼

You need to disable system-level hooks in yka-code environments to prevent automated checks from blocking specific actions. Disabling hooks provides control over execution flows, allowing you to bypass gates like pre-pr checks when necessary.