From faultline
Lists recent unresolved errors from a Faultline instance and prompts the user to investigate a specific error group.
How this skill is triggered — by the user, by Claude, or both
Slash command
/faultline:recentThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Call the `list_error_groups` MCP tool with `status: "unresolved"` and the default limit.
Call the list_error_groups MCP tool with status: "unresolved" and the default limit.
Format the result as a short table — one line per group with: id | exception_class | count | last_seen (relative time like "5m ago"). After the table, ask the user which one they want to investigate. If the user picks one, follow the faultline:debugging skill to dig in.
npx claudepluginhub dlt/faultline --plugin faultlineWalks through unresolved Faultline error groups one at a time, prompting to investigate, resolve, ignore, file a GitHub issue, skip, or stop.
Triage PostHog error tracking issues for daily or on-call review. Surfaces new and high-impact issues ranked by users affected, with links to replays and next-action suggestions.
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.