# global-hook-setup

> Use when setting up global hooks for Claude Code enforcement. Load when ~/.claude/hooks/ is missing or incomplete, or when explicitly requested. Installs 7 project-agnostic hooks (state transitions, git hygiene, outcome tracking). Run once per machine.

- Author: ingpoc
- Repository: ingpoc/agent-harness
- Version: 20251230153013
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-06
- Source: https://github.com/ingpoc/agent-harness
- Web: https://mule.run/skillshub/@@ingpoc/agent-harness~global-hook-setup:20251230153013

---

---
name: global-hook-setup
description: "Use when setting up global hooks for Claude Code enforcement. Load when ~/.claude/hooks/ is missing or incomplete, or when explicitly requested. Installs 7 project-agnostic hooks (state transitions, git hygiene, outcome tracking). Run once per machine."
keywords: hooks, global, setup, enforcement, state-machine, git
---

# Global Hook Setup

One-time setup for global Claude Code hooks. These hooks work across all projects.

## Purpose

Installs 7 project-agnostic hooks that enforce DESIGN-v2 determinism:
- State machine integrity
- Git hygiene
- Learning layer (outcome tracking)
- Session checkpoints

## When to Use

| Situation | Action |
|-----------|--------|
| First time setup | Run full setup |
| ~/.claude/hooks/ missing | Run full setup |
| After updating hooks | Re-run setup |
| Manual verification | Run verify script |

## Quick Check

```bash
# Check if global hooks exist
ls ~/.claude/hooks/
```

Expected output:
```
verify-state-transition.py
require-commit-before-tested.py
require-outcome-update.py
link-feature-to-trace.py
remind-decision-trace.sh
session-end.sh
feature-commit.sh
```

## Setup Steps

### 1. Install Hooks

```bash
~/.claude/skills/global-hook-setup/scripts/setup-global-hooks.sh
```

This creates:
- `~/.claude/hooks/` directory
- 7 hook files
- Executable permissions (chmod +x)

### 2. Verify Installation

```bash
~/.claude/skills/global-hook-setup/scripts/verify-global-hooks.sh
```

## Hooks Installed

| Hook | Purpose | Blocks? |
|------|---------|---------|
| `verify-state-transition.py` | Valid state transitions only | Yes |
| `require-commit-before-tested.py` | Git clean before tested | Yes |
| `require-outcome-update.py` | Update trace outcome | Yes |
| `link-feature-to-trace.py` | Auto-link features | No |
| `remind-decision-trace.sh` | Remind to log decisions | No |
| `session-end.sh` | Checkpoint commit | No |
| `feature-commit.sh` | Feature commit helper | No |

## Exit Criteria (Code Verified)

```bash
# Directory exists
[ -d ~/.claude/hooks ]

# All hooks exist and executable
[ -x ~/.claude/hooks/verify-state-transition.py ]
[ -x ~/.claude/hooks/require-commit-before-tested.py ]
[ -x ~/.claude/hooks/require-outcome-update.py ]
[ -x ~/.claude/hooks/link-feature-to-trace.py ]
[ -x ~/.claude/hooks/remind-decision-trace.sh ]
[ -x ~/.claude/hooks/session-end.sh ]
[ -x ~/.claude/hooks/feature-commit.sh ]

# Verify script passes
~/.claude/skills/global-hook-setup/scripts/verify-global-hooks.sh
```

## Scripts

| Script | Purpose |
|--------|---------|
| `setup-global-hooks.sh` | Main setup (copy + chmod) |
| `verify-global-hooks.sh` | Verify all hooks installed |
| `install-hooks.sh` | Copy from templates |

## Troubleshooting

| Problem | Solution |
|---------|----------|
| Hooks not found | Re-run setup script |
| Permission denied | Run: `chmod +x ~/.claude/hooks/*` |
| Verification fails | Check hook syntax, ensure python3 available |
| Already exists | Setup is idempotent, safe to re-run |

## Next Steps

After global hooks: Set up project-specific hooks with `project-hook-setup` skill.