hooks

Create and manage event-driven hooks for Claude Code workflows.

2|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/RockaRhymeLLC/kithkit --skill hooks-rockarhymellc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hooks
Source: https://github.com/RockaRhymeLLC/kithkit/tree/main/.claude/skills/hooks
Command: npx skills add https://github.com/RockaRhymeLLC/kithkit --skill hooks-rockarhymellc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines your development and automation workflows by allowing you to trigger custom actions (like running scripts or LLM prompts) at specific points within your Claude Code sessions.

Core Features & Use Cases

  • Event-Driven Automation: Set up hooks to run commands or prompts before/after tool usage, at session start/end, or upon user input.
  • Customizable Workflows: Integrate shell scripts for pre-validation, auto-formatting, or LLM prompts for intelligent decision-making.
  • Use Case: Automatically run a linter on code files before they are written or edited, ensuring code quality without manual intervention.

Quick Start

Use the hooks skill to create a PreToolUse hook that runs a bash script named 'pre_check.sh' before any Bash tool is executed.

Frequently Asked Questions about hooks

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

FAQPage Schema
How do I automate workflows by running a script before a tool executes in Claude Code?

Event-driven automation in Claude Code hooks triggers shell commands or LLM prompts before or after tool usage. You configure PreToolUse hooks in user and project settings to execute bash scripts automatically, enabling pre-validation or auto-formatting without manual intervention.

What is event-driven workflow automation in Claude Code sessions?

Event-driven workflow automation in Claude Code sessions executes custom shell commands or LLM prompts based on session lifecycle events, tool usage, and permission requests. Hooks integrate with user and project settings for persistent configuration, allowing scripts to run automatically at specific session points.

Can I use LLM prompts for intelligent decision-making within Claude Code hooks?

Claude Code hooks support LLM prompts for intelligent decision-making alongside shell commands. You can configure event-driven hooks to trigger LLM prompts for automated decision-making during tool usage, session start or end, and upon user input, integrating these workflows into project settings.

What's the best way to automatically run a linter on code files before they are edited?

Automatically running a linter on code files is achieved by setting up a PreToolUse hook in Claude Code. This event-driven automation triggers a bash script before file writes or edits, ensuring code quality and pre-validation without manual intervention during your development workflow.

Do I need project settings to persist event-driven hook configurations across Claude Code sessions?

Project settings and user settings are required to persist event-driven hook configurations across Claude Code sessions. The hooks skill integrates directly with these settings files, ensuring your automated workflows, shell commands, and LLM prompts remain active for future tool usage and lifecycle events.

When should I not use event-driven hooks for workflow automation?

Event-driven hooks for workflow automation are not suitable for one-off manual tasks or processes requiring complex interactive debugging. Hooks excel at persistent, event-driven execution of shell commands and LLM prompts triggered by tool usage and session lifecycle events configured in project settings.