Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From faultline
Walks through unresolved Faultline error groups one at a time, prompting to investigate, resolve, ignore, file a GitHub issue, skip, or stop.
npx claudepluginhub dlt/faultline --plugin faultlineHow this skill is triggered — by the user, by Claude, or both
Slash command
/faultline:triageThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Batch-groom the unresolved error queue.
Lists recent unresolved errors from a Faultline instance and prompts the user to investigate a specific error group.
Automatically triages errors from Sentry or logs, cross-references git history/open PRs/codebase, prioritizes by severity, and opens fix PRs.
Finds and fixes production issues using Sentry's MCP tools. Analyzes stack traces, breadcrumbs, and traces to identify root causes.
Share bugs, ideas, or general feedback.
Batch-groom the unresolved error queue.
list_error_groups with status: "unresolved" and the default limit. If the list is empty, say so and stop.id | exception_class | count | last_seen.exception_class, message, file_path:line_number, occurrence_count, last_seen_at.
b. Ask which of these to do: investigate / resolve / ignore / file-issue / skip / stop.
c. Act on the user's choice:
investigate — follow the faultline:debugging skill (get_occurrence for the latest), then return to the next group.resolve — call resolve_error_group (optionally prompt for a note).ignore — call ignore_error_group.file-issue — call create_github_issue.skip — move on without mutating.stop — exit the loop.If any mutating call returns "Tool disabled: mcp_readonly is true", stop the loop and tell the user to set c.mcp_readonly = false — there is no point continuing without mutation rights.