audit-hooks

Audit Claude hooks from settings.json files and generate a structured hygiene report.

2|Updated Dec 20, 2020
One-click install
npx skills add https://github.com/buvis/home --skill audit-hooks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-hooks
Source: https://github.com/buvis/home/tree/main/.claude/skills/audit-hooks
Command: npx skills add https://github.com/buvis/home --skill audit-hooks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate the health of hooks configured in Claude's global and project settings, enabling quick debugging after edits and when tool calls feel slow.

Core Features & Use Cases

  • Validate existence, permissions, silent failure suppression, and performance concerns for hooks defined in both ~/.claude/settings.json (global) and .claude/settings.json in the current project (project).
  • Build a flat list of hook entries grouped by event and matcher, to detect coverage gaps and potential duplicates across sources.
  • Produce a structured hygiene report detailing findings (missing scripts, non-executable files, anti-patterns, and slow operations) with actionable remediation guidance.

Quick Start

Run the audit-hooks command to scan all configured hooks and generate a hygiene report.

Frequently Asked Questions about audit-hooks

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

FAQPage Schema
How do I audit Claude hooks in settings.json for missing scripts or errors?

Auditing Claude hooks involves scanning global and project settings.json files to build a flat list of entries, checking for missing scripts, non-executable files, and anti-patterns to generate a structured hygiene report.

Why does my Claude hook configuration cause slow tool calls and how can I diagnose it?

Diagnosing slow tool calls requires auditing hook configurations for performance issues by inspecting settings.json entries for timeouts and slow operations, then grouping findings by event and matcher to pinpoint bottlenecks.

What is a Claude hook anti-pattern and when do I need to validate hook health?

A Claude hook anti-pattern is a configuration flaw like silent failure suppression or non-executable scripts. You need to validate hook health after editing settings.json or when tool calls feel slow.

Does the hook audit check both global and project settings.json sources?

Yes, the hook audit checks both global ~/.claude/settings.json and project .claude/settings.json sources. It builds a flat list of hook entries including event type, matcher, command, timeout, and source.

What's the best way to find duplicate hook configurations across different settings sources?

The best way to find duplicate hook configurations is to run an audit that builds a flat list of hook entries grouped by event and matcher, detecting coverage gaps and duplicates across global and project sources.