Help us improve
Share bugs, ideas, or general feedback.
From faultline
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.
npx claudepluginhub dlt/faultline --plugin faultlineHow this skill is triggered — by the user, by Claude, or both
Slash command
/faultline:debug <error-group-id><error-group-id>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Investigate Faultline error group $ARGUMENTS using the `faultline:debugging` skill's investigation order:
Lists recent unresolved errors from a Faultline instance and prompts the user to investigate a specific error group.
Analyzes production errors in distributed systems, performs root-cause analysis on incidents, and recommends observability, logging, and tracing improvements.
Detects and diagnoses application failures by analyzing error logs, stack traces, and system state. Useful when debugging crashes or production incidents.
Share bugs, ideas, or general feedback.
Investigate Faultline error group $ARGUMENTS using the faultline:debugging skill's investigation order:
get_error_group with id: $ARGUMENTS.recent_occurrences array.get_occurrence with that id for the full backtrace, captured local variables, and request context.list_traces filtered to the relevant endpoint, then get_trace for span detail.After the investigation, propose a fix with citations to specific files and line numbers from the backtrace, grounded in the local variable values.