hook-diagnostics

1# Hook Diagnostics
2 
3Diagnose hook integration issues between Claude Code and the Agent Monitor.
4 
5## Input
6 
7The user provides: **$ARGUMENTS**
8 
9This may be:
10- "full" or empty (default: run all diagnostics)
11- "install" to check hook installation only
12- "connectivity" to check dashboard connectivity only
13- "events" to check event delivery only
14 
15## Procedure
16 
17Run diagnostic checks in this order:
18 
19### 1. Hook Installation Check
20Verify hooks are installed in Claude Code settings:
21 
22```bash
23# Check if hooks exist in Claude Code settings
24cat ~/.claude/settings.json | jq '.hooks // empty'
25```
26 
27Verify:
28- All 7 expected hook types are registered: `PreToolUse`, `PostToolUse`, `Stop`, `SubagentStop`, `Notification`, `SessionStart`, `SessionEnd`
29- Hook commands point to the correct handler script path
30- Handler script exists and is readable at the configured path
31 
32### 2. Dashboard Connectivity
33Test that the dashboard API is reachable:
34 
35```bash
36curl -sf http://localhost:4820/api/health
37```
38 
39Verify:
40- Dashboard responds with 200 OK
41- Response includes expected health fields
42- WebSocket endpoint is accessible
43 
44### 3. Hook Handler Validation
45Check the hook handler script:
46 
47```bash
48# Verify handler exists and is executable
49ls -la <handler-path>
50# Syntax check
51node --check <handler-path>
52```
53 
54### 4. Event Delivery Test
55Send a test event and verify it arrives:
56 
57```bash
58echo '{"hook_type":"test","session_id":"diag-test","data":{}}' | \
59  curl -sf -X POST http://localhost:4820/api/hooks/event \
60…