Stats
Actions
Tags
From faultline
Reopens a previously resolved Faultline error group by ID. Useful when a regression brings back an error or a group was resolved by mistake.
How this skill is triggered — by the user, by Claude, or both
Slash command
/faultline:unresolve <error-group-id><error-group-id>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Unresolve Faultline error group `$ARGUMENTS`.
Unresolve Faultline error group $ARGUMENTS.
get_error_group with the id and show: exception_class, message, occurrence_count, last_seen_at, current status, resolved_at.status is already unresolved, stop and tell the user — nothing to do.status is ignored, mention that unresolving will move it back to active triage. Ask the user to confirm.unresolve_error_group with id.resolved_at should be cleared in the response.Common reasons to unresolve: a regression brought the error back, or the group was resolved by mistake. If the user mentions a new occurrence, Faultline auto-reopens resolved groups when they reoccur (ErrorGroup.find_or_create_from_exception), so explicit unresolve is rarely needed for active errors — verify before mutating.
If the tool returns error: "Tool disabled: mcp_readonly is true", tell the user to set c.mcp_readonly = false in their Faultline initializer.
npx claudepluginhub dlt/faultline --plugin faultlineResolves a Faultline error group by ID with an optional note. Confirms current status before mutating and warns if the tool is in read-only mode.
Consolidates PostHog error tracking issues split by fingerprint noise. Merges duplicates and creates grouping rules to prevent future splits.
Retrieves Bugsnag organizations, projects, errors, details, events, comments, stats; analyzes trends; resolves errors and adds comments via Ruby API scripts.