What is a Claude Code Hook?

A hook is a shell command or script that triggers automatically before or after Claude Code performs a specific action, such as writing a file or executing a bash command.

Where are hook configurations stored?

Hooks can be configured in a plugin's .claude-plugin/hooks.json file, a user-level .claude/hooks.json file, or inline within a plugin.json manifest.

Will hooks slow down my development process?

While hooks do block execution, following best practices like keeping scripts lightweight (e.g., using fast linters rather than full test suites) ensures minimal impact on performance.

How do I access file paths in a hook?

You can use dynamic variables like {{file_path}} within your hook configuration, which Claude automatically substitutes with the relevant context during execution.

Can I use hooks to prevent Claude from making mistakes?

Yes, 'before' hooks can block tool execution if they return a non-zero exit code, allowing you to validate commands or code changes before they are applied.

Automated Workflow Hooks

Name: Automated Workflow Hooks
Author: vinnie357

byvinnie357

Productivity & Workflow

Automates shell command execution in response to Claude Code tool calls, prompts, and lifecycle events.

About

This skill provides a comprehensive framework for implementing event-driven automations within the Claude Code environment. It enables developers to define custom pre- and post-execution triggers for various tools—such as file writing, editing, and bash commands—allowing for seamless integration of linting, formatting, security validations, and external logging. By utilizing these hooks, users can enforce project-specific standards, prevent dangerous operations, and build robust, automated developer workflows that respond intelligently to every AI interaction.

Key Features

Execution blocking capabilities via shell exit codes for validation
Lifecycle event management for plugin installation and uninstallation
Before and after triggers for specific tool calls like Read, Write, and Bash
Support for both plugin-specific and global user-level configurations
Dynamic variable substitution for file paths, content, and user prompts
0 GitHub stars

Use Cases

Automatically run Prettier and ESLint after Claude modifies code files
Create automatic file backups before any destructive edits are performed
Block dangerous Git operations like force pushes to protected branches

About

Key Features

Execution blocking capabilities via shell exit codes for validation
Lifecycle event management for plugin installation and uninstallation
Before and after triggers for specific tool calls like Read, Write, and Bash
Support for both plugin-specific and global user-level configurations
Dynamic variable substitution for file paths, content, and user prompts
0 GitHub stars

Use Cases

Automatically run Prettier and ESLint after Claude modifies code files
Create automatic file backups before any destructive edits are performed
Block dangerous Git operations like force pushes to protected branches