error-tracking-specialist

Analyze stack traces and error context to triage production application errors.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Whaleylaw/llm-lawyer --skill error-tracking-specialist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-tracking-specialist
Source: https://github.com/Whaleylaw/llm-lawyer/tree/main/.claude/skills/error-tracking-specialist
Command: npx skills add https://github.com/Whaleylaw/llm-lawyer --skill error-tracking-specialist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers and ops teams quickly investigate, triage, and remediate production application errors by guiding stack trace analysis, reproductions, context enrichment, and monitoring configuration to reduce user impact and regression time.

Core Features & Use Cases

  • Stack trace analysis & debugging: Walk through error messages and stack traces to identify the offending module, file, and line.
  • Reproduction guidance: Use error context (breadcrumbs, requests, user state) to reproduce issues locally or in staging.
  • Monitoring setup & tuning: Provide step-by-step instructions to configure Sentry/Rollbar SDKs, release tracking, alerts, and beforeSend filters.
  • Triage & prioritization: Group similar errors, evaluate user impact, assign severity (P0–P3), and recommend remediation or mitigations.
  • Best practices: Advice on adding user context, source maps, rate limiting, scrubbing sensitive data, and alert thresholds.

Quick Start

Analyze the top Sentry error from the last 24 hours, identify the root cause, list reproduction steps, and recommend priority and mitigations.

Frequently Asked Questions about error-tracking-specialist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze a stack trace to find the root cause of a production error?

Applying error triage involves grouping similar stack traces, evaluating user impact, and assigning severity from P0 to P3. This error triage process helps prioritize user-impacting failures and recommends appropriate mitigations.

How do I reproduce a Sentry error using breadcrumbs and user context?

Configuring error monitoring involves setting up Sentry or Rollbar SDKs, release tracking, and alert thresholds. Proper monitoring setup and tuning ensure you capture accurate stack traces and receive timely alerts for production crashes.

What is the best way to group similar errors and assign priority during triage?

The best way to triage errors is to group similar stack traces together, evaluate the frequency and user impact, and assign a severity level from P0 to P3. This grouping recommendation streamlines prioritization and remediation.

How do I configure Sentry release tracking and alerts for production web services?

Configuring Sentry release tracking requires setting up the SDK, defining alert thresholds, and applying beforeSend filters. This monitoring setup links production errors to specific releases and notifies you of user-impacting failures.

Does this approach work with Rollbar for debugging backend service crashes?

Yes, this triage approach works with Rollbar for backend service crashes by analyzing stack traces and error context. It applies to any production web or backend services instrumented with Rollbar or similar error monitoring tools.