debugging-with-undo

Included with Lifetime

$97 forever

Debug programs using Undo time travel debugging. Record flaky tests, intermittent failures, race conditions, or bugs that don't reproduce reliably. Analyze recordings by traveling backwards through execution history. Use when the user mentions debugging, flaky tests, intermittent bugs, race conditions, `.undo` files (Undo recordings), or asks why something happened in an actual run. This can provide similar results as adding logging statements, but without modifying the code or needing to re-run the program multiple times.

Code Review

What this skill does


# Debugging with Undo time travel debugger

Undo provides time travel debugging for Linux programs. This Skill guides you to:
1. **Record** program execution to capture failures (especially intermittent ones)
2. **Debug** recordings by traveling backwards through execution history

## When to record (use `record` MCP tool)

Record program execution when the user:
- Has a **flaky test** or **intermittent failure** that doesn't reproduce reliably
- Mentions **race conditions**, **threading issues**, or **concurrency bugs**
- Wants to **capture a failure** for later analysis
- Needs **deterministic replay** of a bug

Undo captures the exact execution including thread interleavings, making even race conditions
reproducible.

## When to debug (use debugging MCP tools)

Debug a recording when the user:
- Has a **`.undo` recording file** to investigate
- Asks **"why did this happen"** or **"how did this value get set"**
- Wants **root cause analysis** on a captured failure
- Needs to understand execution **backwards** from a crash or assertion

## Workflow

1. **If no recording exists**: Use `record` MCP tool to capture the failure
2. **If recording exists**: Use debugging MCP tools to analyze it
3. **Work backwards**: Start at the end (where the bug manifested), trace backwards

## Important

- **Never access `.undo` files directly** - they are opaque binary recordings
- **Never invoke `udb`, `live-record`, or `undo` via Bash** - use the Undo MCP tools

Files: 1

Size: 2.0 KB

Complexity: 10/100

Category: Code Review

Source: https://github.com/undoio/addons/tree/main/skills/debugging-with-undo

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts