list-hooks

List all configured hooks by parsing the settings.json file to enumerate active hook configurations, displaying each hook's event, matcher pattern, and script names for review. It generates a structured catalog of all active hooks.

Yes, you can detect orphaned scripts by scanning the hooks/scripts directory and cross-referencing them against parsed settings.json configurations to identify unreferenced scripts, providing a clear report for cleanup or debugging.

Audit local hook overrides by detecting and reporting local-only hooks from settings.local.json, comparing them against the main settings.json to identify discrepancies and active local configurations for debugging.

Catalog Claude hooks and their matchers by parsing JSON hook configurations to generate a structured, formatted output that can be reviewed or pasted directly into project documentation for auditing active events and scripts.

Yes, it works with PreToolUse, PostToolUse, and other hook types by reading the settings.json hooks object to display each hook's event type, matcher pattern, and associated script names in the generated catalog.