From faultline
Resolves 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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/faultline:resolve <error-group-id> [note]<error-group-id> [note]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Resolve Faultline error group from `$ARGUMENTS`. The first token is the group id; the rest (if any) is the note.
Resolve Faultline error group from $ARGUMENTS. The first token is the group id; the rest (if any) is the note.
get_error_group with the id and show the user: exception_class, message, occurrence_count, last_seen_at, and current status.status is already resolved or ignored, stop and tell the user — don't re-resolve.resolve_error_group with id and note (omit note if none was given).If the tool returns error: "Tool disabled: mcp_readonly is true", tell the user to set c.mcp_readonly = false in their Faultline initializer — this is a mutating tool and is off by default.
npx claudepluginhub dlt/faultline --plugin faultlineReopens a previously resolved Faultline error group by ID. Useful when a regression brings back an error or a group was resolved by mistake.
Consolidates PostHog error tracking issues split by fingerprint noise. Merges duplicates and creates grouping rules to prevent future splits.
Guides resolving Blumira security findings with correct resolution types, metrics impact, API usage (e.g., blumira_findings_resolve), workflows, and bulk false positive handling.