global-hook-setup

Install and configure global Claude Code hooks across machines.

9|Updated Dec 13, 2025
One-click install
npx skills add https://github.com/ingpoc/SKILLS --skill global-hook-setup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: global-hook-setup
Source: https://github.com/ingpoc/SKILLS/tree/main/global-hook-setup
Command: npx skills add https://github.com/ingpoc/SKILLS --skill global-hook-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates the one-time setup and ongoing governance of global Claude Code hooks to ensure consistent behavior across machines and environments.

Core Features & Use Cases

  • Installs and configures a set of global hooks that enforce design determinism, git hygiene, and outcome tracking across projects.
  • Provides a suite of scripts (install, configure, verify, and validate) to streamline and guard the setup process.
  • Supports extension to project-specific hooks, enabling scalable governance across teams and projects.

Quick Start

Run the global hook setup script to install the hooks and configure your settings.

Frequently Asked Questions about global-hook-setup

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

FAQPage Schema
How do I install global Claude Code hooks across multiple machines?▼

You can automate global Claude Code hook installation by running the provided setup-global-hooks.sh script. It configures settings.json and populates the ~/.claude/hooks/ directory to ensure consistent behavior across environments.

What are global Claude Code hooks used for?▼

Global Claude Code hooks are used to enforce design determinism, git hygiene, and outcome tracking across all projects. They provide a centralized governance mechanism to maintain consistent development environments on any machine.

How do I verify that my global hooks are configured correctly?▼

Verify global hooks by running the verify-global-hooks.sh and validate-settings.py scripts. These tools check that hooks are present in ~/.claude/hooks/ and properly configured within your settings.json file.

Do I need a specific directory structure to configure global hooks?▼

Yes, configuring global hooks requires a properly structured ~/.claude/settings.json file and the presence of the ~/.claude/hooks/ directory. The install-hooks.sh script helps create and populate this required structure.

What should I do if my global hooks are missing after an update?▼

If global hooks are missing after an update, rerun the setup-global-hooks.sh script. This re-installs the hooks, updates configurations in settings.json, and verifies that all governance mechanisms are present and functioning.

Can I extend global hooks to enforce project-specific rules?▼

Yes, you can extend global hooks to support project-specific enforcement. This enables scalable governance across teams and projects while maintaining the baseline design determinism and git hygiene established by the global configuration.