Stats
Actions
Tags
From faultline
Finds Faultline error groups that started appearing after a deploy timestamp, helping identify regressions introduced by a release.
How this skill is triggered — by the user, by Claude, or both
Slash command
/faultline:since-deploy <iso-timestamp or relative like "2h ago"><iso-timestamp or relative like "2h ago">The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Identify groups that began firing after a deploy or release.
Identify groups that began firing after a deploy or release.
$ARGUMENTS to an ISO 8601 timestamp.
30m ago, 2h ago, yesterday at 3pm), convert it.list_error_groups with since: <timestamp> and the default limit.first_seen_at >= <timestamp> — these are new groups, not just groups that were also hit before the deploy. This is the regression signal.id | exception_class | message | first_seen_at | occurrences_count. Sort by first_seen_at ascending so the earliest regression is first./debug <id> — its backtrace will point at the code introduced by the deploy.If the result is empty, the deploy looks clean from Faultline's perspective. Mention that errors filtered by ignored_exceptions won't show up here either.
npx claudepluginhub dlt/faultline --plugin faultlineQueries Faultline for recently active error groups ranked by occurrence count, with a configurable lookback window. Flags brand-new errors and offers drill-down.
Prioritizes and triages PostHog error tracking issues by recency, users affected, and trend spikes. Points to linked replays and suggests next actions.
Investigates recent errors and exceptions in Sentry projects: fetches issues via MCP, analyzes frequency, trends, stack traces, user impact, and suggests fixes for quick triage.