skills.rest
astashov
astashovCOMMUNITY
Explore all skills by this author →
Website𝕏@anton_astashovGitHub

debug-rollbar

Investigates production Rollbar errors interactively through occurrence data, user context, and root-cause analysis.

692|107|Updated Feb 29, 2020
Search Tags:#stack trace#Debugging#Root Cause Analysis#error tracking#production errors#rollbar#Monitoring
One-click install
npx skills add https://github.com/astashov/liftosaur --skill debug-rollbar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-rollbar
Source: https://github.com/astashov/liftosaur/tree/main/.claude/skills/debug-rollbar
Command: npx skills add https://github.com/astashov/liftosaur --skill debug-rollbar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Production errors reported in Rollbar are hard to diagnose without context: you need to know how widespread an error is, which users it hits, what they were doing, and what the app state looked like at crash time. This Skill walks you through a structured, conversational investigation of a Rollbar error so you can reach a fix-or-ignore decision with evidence.

Core Features & Use Cases

  • Flexible input resolution: Accepts an occurrence id, item id, item counter, or Rollbar URL and resolves it to the right item and occurrences via the Rollbar API.
  • Blast-radius assessment: Fetches item overview and recent instances to determine how many users are affected, whether it is a regression tied to a code version, and which platforms are involved.
  • Deep user context: Pulls captured client state (last actions, last state), user event timelines, server logs, and storage snapshots via Lambda scripts to reconstruct what happened before the error.
  • Guided decision-making: Presents root-cause hypotheses with cited evidence, then helps you fix the bug, add the error to the ignore list, or instrument the code with targeted debug logging.
  • Use Case: You get a Rollbar alert URL in Slack. Paste it into this Skill, and it will fetch the occurrence, show that 12 users hit it after the latest deploy, replay one user's actions from captured state, pinpoint the failing reducer, and propose a minimal fix with a regression test.

Quick Start

Ask the assistant to debug Rollbar occurrence 12345678901234567 and investigate what caused it.

Frequently Asked Questions about debug-rollbar

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

FAQPage Schema
How do I investigate a Rollbar error from a URL or occurrence id?▼

Provide the Rollbar URL, occurrence id, item id, or item counter as the argument. The Skill resolves the input type automatically, fetches the item and occurrence data through the Rollbar API, and stages artifacts under a .tmp directory for analysis.

What do I need to set up before debugging Rollbar errors with this workflow?▼

You need the ROLLBAR_READ_TOKEN environment variable set for Rollbar API access. User-context lookups also rely on Lambda scripts in the repository run via npm run r, so the repo and its dependencies must be available locally.

Can I see what a user was doing right before the error occurred?▼

Yes. When the occurrence has a person id, the Skill fetches the user's events timeline, server logs for the error date, current storage, and storage snapshots. Captured exceptions also include the last actions and full client state at crash time.

How do I stop a noisy unactionable error from appearing in Rollbar?▼

For noise like browser extensions or transient network errors, the Skill appends a unique, specific substring of the error message to the exceptionIgnores list in src/utils/rollbar.ts. It warns against ignoring patterns broad enough to hide real errors.

What is the difference between debug-rollbar and fix-rollbar?▼

debug-rollbar is a conversational, multi-stage investigation that confirms direction with you before each step and never changes code without presenting root-cause analysis first. fix-rollbar is a straight fetch-and-fix flow for a single occurrence.

What should I do when the root cause of an error stays inconclusive?▼

The Skill recommends instrumenting suspect code paths with lgDebug calls scoped to the affected user's tempUserId, which log on both web and native. After deploy and reproduction, you review the events timeline and remove the instrumentation once concluded.

Related Skills

Explore More Software Engineering Skills→
ESO-ToolkitESO-Toolkit
2

rollbar

Search, view, resolve, assign, and comment on Rollbar production errors.

Official
Intermediate
Devin-AXISDevin-AXIS
5.3k

sentry-fix-verification

Verify production fixes by comparing Sentry issue events before and after a release.

Community
Basic
jimmy071919jimmy071919

analytics-instrumentation

Add PostHog analytics tracking to Opik frontend and backend features.

Community
Intermediate
nuts-and-bolts-ainuts-and-bolts-ai

rollbar

Query the Rollbar API to list errors, retrieve item details, and fetch stack traces.

Official
Intermediate