hooks-status

Analyzes hooks.jsonl audit logs to report hook trigger counts, overrides, and dead hooks.

Updated May 27, 2026
One-click install
npx skills add https://github.com/jokerman89/lintel --skill hooks-status-jokerman89
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hooks-status
Source: https://github.com/jokerman89/lintel/tree/main/skills/hooks-status
Command: npx skills add https://github.com/jokerman89/lintel --skill hooks-status-jokerman89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams running Lintel's 33 hooks have no visibility into which hooks actually fire, which get overridden repeatedly, and which are dead weight. This Skill reads the hooks.jsonl audit log and turns raw hook events into an actionable observation report. ## Core Features & Use Cases - Trigger Aggregation: Counts hook triggers over a configurable time window and surfaces a table of hook name, trigger count, and last trigger timestamp. - Override Pattern Detection: Groups override events by hook and reason, flagging any hook overridden more than 5 times in 7 days as a friction signal. - Dead Hook Detection: Cross-references installed hooks against trigger history to flag hooks with zero triggers over N days as cleanup candidates. - Use Case: Before a maintenance pass, run the dead-hook view with a 90-day window to identify hooks that never fire, then validate their install state before removing them. ## Quick Start Ask the agent to run the hooks-status skill with the triggers view over the last 30 days to see which hooks actually fire.

Frequently Asked Questions about hooks-status

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

FAQPage Schema
How do I check which hooks are actually firing?▼

Run the hooks-status skill with the --triggers flag and a --days window, such as --triggers --days 30. It parses hooks.jsonl, groups events by hook name, and outputs a table of trigger counts and last trigger timestamps.

How to find dead hooks that never trigger?▼

Use the --dead --days N view, for example --dead --days 90. The skill scans the hooks directory for installed hooks, checks each one's last trigger in hooks.jsonl, and flags any with no trigger in the past N days as cleanup candidates.

Can hooks-status detect hooks being overridden too often?▼

Yes, the --overrides view filters hooks.jsonl for override events, groups them by hook name and reason, and flags any hook overridden more than 5 times in 7 days as a friction signal worth operator review.

Does hooks-status monitor hooks in real time?▼

No, it is retroactive and reads the hooks.jsonl audit log after events occur. Real-time hook watching would require a filesystem watcher like inotify or fswatch, which is outside this skill's scope.

What happens if hooks.jsonl is missing or malformed?▼

If hooks.jsonl does not exist, the skill reports that no hook events have been recorded yet. Malformed JSON lines are skipped, counted, and reported at the end, and the run completes with a DONE_WITH_CONCERNS status.