From faultline
Queries Faultline for recently active error groups ranked by occurrence count, with a configurable lookback window. Flags brand-new errors and offers drill-down.
How this skill is triggered — by the user, by Claude, or both
Slash command
/faultline:spikeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Surface error groups that are firing right now.
Surface error groups that are firing right now.
$ARGUMENTS as the lookback window. Default to 1h. Convert to an ISO 8601 timestamp for "now minus duration".list_error_groups with since: <iso-timestamp> and the default limit. Note: since filters by last_seen_at, so this returns groups that have been hit at least once in the window — not strictly groups that "spiked", but it's the closest available signal.occurrences_count descending and render: id | exception_class | count | first_seen_at | last_seen_at.first_seen_at is inside the window — those are brand-new errors that only started appearing now, which is the strongest spike signal./debug <id>.If you also want a global volume picture, suggest /stats <period> — that one shows time-bucketed counts across the whole instance.
npx claudepluginhub dlt/faultline --plugin faultlineShows time-bucketed error occurrence counts from Faultline. Useful for spotting error volume spikes over a configurable window (1h to all).
Prioritizes and triages PostHog error tracking issues by recency, users affected, and trend spikes. Points to linked replays and suggests next actions.
Queries Lensflare datasets for recent errors and fatals, groups by frequency, fetches traces, and summarizes root causes with failing spans and services. Use for 'what's broken' or vague stack traces.