debug-user

Investigate user-reported issues using server logs, event timelines, storage snapshots, and Rollbar.

692|107|Updated Feb 29, 2020
One-click install
npx skills add https://github.com/astashov/liftosaur --skill debug-user
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-user
Source: https://github.com/astashov/liftosaur/tree/main/.claude/skills/debug-user
Command: npx skills add https://github.com/astashov/liftosaur --skill debug-user

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Support tickets describing bugs like wrong weights, lost history, or sync failures are hard to reproduce locally. This Skill correlates a user's server-side data — event timelines, DynamoDB storage snapshots, server logs, and Rollbar exceptions — to find the root cause of a reported issue without guessing.

Core Features & Use Cases

  • Event Timeline Analysis: Fetches the last two weeks of client events grouped by day, including errors with Rollbar ids and storage snapshot markers.
  • Storage Snapshot Diffing: Compares storage snapshots from before and after a suspected corruption point to pinpoint data loss.
  • Rollbar Drill-Down: Resolves Rollbar occurrence ids to captured exception state and last user actions for crash investigation.
  • Targeted Instrumentation: Adds user-scoped lgDebug logging to suspect code paths when existing data is inconclusive, then re-checks events after deploy.
  • Use Case: A user emails that their workout weights reset after Tuesday. Run the Skill with their email to pull the events timeline, diff storage snapshots around Tuesday, and identify the exact sync update that corrupted the state.

Quick Start

Ask the assistant to debug the issue for user id abc123 who reports that their workout history disappeared after the last app update.

Frequently Asked Questions about debug-user

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

FAQPage Schema
How do I investigate a user-reported bug from a support email?

Provide the user's id or email plus the issue description. The Skill resolves the user id, fetches the two-week events timeline first, then pulls targeted server logs, storage snapshots, or Rollbar occurrences based on the issue type.

How do I find what corrupted a user's data at a specific point in time?

Fetch storage snapshots from before and after the suspect moment using snapshot ids from the events timeline, then compare targeted fields between them. Snapshot ids come from the safesnapshot and mergesnapshot lines in events.md.

Can I look up a user by email instead of user id?

Yes, email addresses are resolved to user ids via the get_user_id_by_email script. Rollbar occurrence ids are also accepted, resolving the user from the occurrence's person.id field.

What do I do when the logs and events don't explain the issue?

Add lgDebug calls with the user's id at suspect code paths, which log events only for that specific user on web and native. After the developer deploys and the user reproduces the issue, re-fetch the events timeline to see the new instrumentation data.

Why can't I query Rollbar with RQL to find a user's errors?

RQL is unavailable on the current Rollbar plan. The fallback pages through recent occurrences via the instances API and filters by person id, which is only practical for recent crashes within roughly 10-20 pages.