hooks-list

List enabled and disabled yka-code hooks from the state file and YKA_HOOKS_BYPASS.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/youssefKadaouiAbbassi/yka-code --skill hooks-list
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hooks-list
Source: https://github.com/youssefKadaouiAbbassi/yka-code/tree/main/skills/hooks-list
Command: npx skills add https://github.com/youssefKadaouiAbbassi/yka-code --skill hooks-list

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the need to quickly view the current state of yka-code hooks, distinguishing between those that are enabled and disabled.

Core Features & Use Cases

  • Hook Status Overview: Provides a summary of all yka-code hooks, highlighting which are currently active.
  • Environmental Variable Check: Includes the state file and the YKA_HOOKS_BYPASS environment variable in the assessment.
  • System Path Verification: Ensures that yka-code-setup is available on the system's PATH before executing the hook list command.

Quick Start

Run the 'hooks-list' skill to display the current status of yka-code hooks.

Frequently Asked Questions about hooks-list

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

FAQPage Schema
How do I list enabled and disabled yka-code hooks?

To list yka-code hooks, the system reads the state file and the YKA_HOOKS_BYPASS environment variable to distinguish between enabled and disabled hooks, then displays the current status overview.

What environment variables are checked to display yka-code hook status?

The YKA_HOOKS_BYPASS environment variable is checked alongside the state file to determine which yka-code hooks are currently enabled or disabled before displaying the status.

Do I need yka-code-setup on my PATH to view active hooks?

Yes, you need yka-code-setup available on the system's PATH. The system verifies its presence before executing the command to list enabled and disabled yka-code hooks.

How does the hook list command determine if a hook is active?

The hook list command determines active status by examining the state file and checking the YKA_HOOKS_BYPASS environment variable to see if hooks are bypassed or currently enabled.

Why does my yka-code hook list not show any active hooks?

If no active hooks appear, the state file may be empty or the YKA_HOOKS_BYPASS environment variable might be set to bypass hooks, overriding their enabled status during the system status check.

Can I check yka-code hook status without installing yka-code-setup?

No, you cannot check hook status without yka-code-setup. The process explicitly verifies that yka-code-setup is present on the system's PATH before executing the hook list command.