From claude-code-hooks
Diagnoses Claude Code hooks setup by checking active hooks, file permissions, dependencies (jq, python3, node), env vars, settings.json integration, and recent activity logs.
npx claudepluginhub yurukusa/claude-code-hooks --plugin claude-code-hooksThis skill uses the workspace's default tool permissions.
Run a diagnostic check on the user's Claude Code hooks setup.
Runs comprehensive diagnostics on Claude Code environment: plugins, settings, hooks, MCP servers. Identifies issues, supports --fix and --verbose.
Guides setup of Claude Code Hooks for production safety, selecting profiles (Minimal, Standard, Autonomous), configuring env vars like CC_CONTEXT_MISSION_FILE, and running verification tests.
Audits Claude Code hooks for config validity, script structure, matchers, env vars, decisions, and tests. Run after hook creation, before releases, or for periodic checks.
Share bugs, ideas, or general feedback.
Run a diagnostic check on the user's Claude Code hooks setup.
Hook files exist and are executable
for hook in context-monitor.sh syntax-check.sh activity-logger.sh branch-guard.sh decision-warn.sh cdp-safety-check.sh error-gate.sh no-ask-human.sh proof-log-session.sh session-start-marker.sh; do
if [ -f "${CLAUDE_PLUGIN_ROOT}/hooks/$hook" ]; then
if [ -x "${CLAUDE_PLUGIN_ROOT}/hooks/$hook" ]; then
echo "OK: $hook (executable)"
else
echo "WARN: $hook exists but not executable"
fi
else
echo "MISSING: $hook"
fi
done
Dependencies available
jq — required by most hookspython3 — required by activity-logger, proof-log, context-monitornode — optional, for JS syntax checkingEnvironment variables
Settings.json integration
~/.claude/settings.json for hook entriesRecent activity
Present results as a health report:
=== Claude Code Hooks Health Check ===
Hooks: 8/10 active
Deps: jq ✓ python3 ✓ node ✓
Env: 3/5 configured
Activity: Last entry 2h ago
Overall: HEALTHY (2 warnings)
List any warnings or errors with actionable fix instructions.