Help us improve
Share bugs, ideas, or general feedback.
From faultline
Diffs multiple occurrences of the same Faultline error group to identify varying inputs, locals, and request params that distinguish failures from successes.
npx claudepluginhub dlt/faultline --plugin faultlineHow this skill is triggered — by the user, by Claude, or both
Slash command
/faultline:compare <error-group-id> [count, default 3]<error-group-id> [count, default 3]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Compare occurrences of the same group to spot which inputs vary between successes and failures.
Investigates a Faultline error group by fetching group details, the most recent occurrence with full backtrace and local variables, and optionally correlated traces for performance issues. Proposes a fix grounded in the data.
Queries Lensflare datasets for recent errors and fatals, groups by frequency, fetches traces, and summarizes root causes with failing spans and services. Use for 'what's broken' or vague stack traces.
Runs or continues differential debugging sessions between implementations, traces, captures, or outputs. Records artifact identities, commands, mismatches, findings, validation, and next probes in durable session logs.
Share bugs, ideas, or general feedback.
Compare occurrences of the same group to spot which inputs vary between successes and failures.
$ARGUMENTS: first token is the group id, optional second token is how many occurrences to compare (default 3, max 10).recent_occurrences with group_id: <id> and limit: <count> to get a list of occurrence ids.get_occurrence to pull the full payload (backtrace, locals, request params, headers).request_method — different endpoints hitting the same fingerprint?If only one occurrence exists for the group, say so — there's nothing to compare. Filtered values will appear as [FILTERED] and shouldn't be flagged as differences (Rails.application.config.filter_parameters + config.sanitize_fields).