debugging

Automate methodical debugging workflows to isolate root causes in software projects.

2|Updated Nov 28, 2025
One-click install
npx skills add https://github.com/joshribakoff/surfsim --skill debugging-joshribakoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/joshribakoff/surfsim/tree/main/.claude/skills/debugging
Command: npx skills add https://github.com/joshribakoff/surfsim --skill debugging-joshribakoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates a systematic debugging workflow to help engineers quickly reproduce, isolate, and verify bugs.

Core Features & Use Cases

  • Decision-tree guided isolation leads from bug reports to root causes with lightweight tests.
  • Structured remediation workflow ensures consistent diagnosis across projects and teams.
  • Dev-state exposure & safe testing practices provide transparent debugging in development environments.

Quick Start

Describe the bug with steps to reproduce and request a structured debugging plan.

Frequently Asked Questions about debugging

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

FAQPage Schema
How do I systematically debug a flaky test to find the root cause?

Systematic debugging isolates root causes fast by applying a decision-tree approach to bug reports and runtime issues. It automates methodical workflows that guide reproduction, isolation, and verification across software projects.

What's the best way to isolate a runtime issue from a vague bug report?

Isolating a runtime issue from a bug report requires structured remediation that guides you through reproduction and verification. A decision-tree approach systematically narrows down the root cause using test-first validation.

How do I create a structured debugging plan for a software project?

You can create a structured debugging plan by describing the bug with reproduction steps. This generates a systematic workflow applying decision-tree isolation and test-first validation to verify the root cause.

How do I safely expose application state during development debugging?

Safely exposing application state during debugging requires dev-state exposure practices tailored for development environments. This enables transparent debugging and safe testing while isolating runtime issues.

Can I use a test-first validation approach to verify bug fixes?

Yes, test-first validation is central to this debugging workflow. You write lightweight tests to reproduce the issue, then use those same tests to verify that your isolated fix resolves the root cause.