hook-audit

To audit hook effectiveness in Claude Code sessions, you can run this skill to analyze performance metrics, detect silent or over-aggressive hooks, identify enforcement gaps, and generate actionable tuning recommendations.

Claude Code hooks may never trigger if they are silent or not properly wired to logging. This skill analyzes session data to identify these silent hooks and recommends wiring them correctly to ensure proper workflow enforcement.

The best way to identify over-aggressive hooks is by analyzing session metrics for high block counts. This skill detects hooks that hinder productivity and provides recommendations to soften their enforcement rules.

To find enforcement gaps, you cross-reference Claude Code rules with actual hook activity. This skill automates that cross-reference process to identify missing rules and recommends adding or hardening specific hooks.

Yes, you can analyze broader Claude Code session workflow metrics including PR lag, CI pass rate, phase skipping, review round distribution, and human-review resolution latency using this skill's retro analytics capabilities.

Yes, performing a hook analysis requires access to Claude Code session data and hook scripts. This data allows the skill to evaluate performance metrics and generate accurate optimization recommendations.