Debugger

Diagnose codebase bugs and propose minimal fixes from error reports.

42|1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/rar-file/surf --skill debugger-rar-file
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Debugger
Source: https://github.com/rar-file/surf/tree/main/skills/debugger
Command: npx skills add https://github.com/rar-file/surf --skill debugger-rar-file

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and fix bugs in codebases with a systematic, methodical approach.

Core Features & Use Cases

  • Systematic debugging workflow: reproduce, isolate, identify, fix, verify.
  • Language-agnostic: applies to script, frontend, backend projects.
  • Use Case: given a failing unit test, you can quickly identify root cause and propose minimal changes.

Quick Start

Describe the bug with any error messages and I will diagnose it and propose a minimal fix.

Frequently Asked Questions about Debugger

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

FAQPage Schema
How do I systematically diagnose and fix bugs in my code?

To diagnose bugs systematically, follow a workflow of reproducing the error, isolating the component, identifying the root cause, applying a minimal fix, and verifying. This language-agnostic approach works across small scripts and large systems.

What do I need to provide to reproduce an unexpected code error?

To reproduce unexpected code behavior, you need to provide a clear error message, exact reproduction steps, and sufficient codebase context. These inputs are required to accurately identify root causes and propose minimal fixes.

Can I use a systematic debugging workflow for frontend and backend projects?

Yes, systematic debugging applies to both frontend and backend projects. This language-agnostic workflow handles debugging tasks across various project types, from small standalone scripts to large complex systems.

What is the best way to find the root cause of a failing unit test?

The best way to find the root cause of a failing unit test is using a methodical debugging workflow. By providing the error message and test context, you can quickly isolate the failure and propose minimal code changes.

Does this debugging approach work without specific code analysis dependencies?

Yes, this debugging approach works without specific code analysis dependencies. It requires no external components, relying solely on clear error messages, reproduction steps, and codebase context to identify root causes.