self-debugging

Diagnose and fix code errors with a repeatable, evidence-based debugging workflow.

1|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/xiaoshuangLi/aibo --skill self-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: self-debugging
Source: https://github.com/xiaoshuangLi/aibo/tree/main/skills/self-debugging
Command: npx skills add https://github.com/xiaoshuangLi/aibo --skill self-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a deterministic, evidence-based approach to debugging code errors, helping developers avoid guesswork and systematically locate root causes.

Core Features & Use Cases

  • Stepwise triage: READ the complete error, LOCATE the exact file and line, view surrounding context, and form a single hypothesis.
  • Targeted fixes: apply only one change at a time and re-test to confirm impact.
  • Multi-language support: effective across TypeScript/JavaScript, Python, and runtime exceptions.
  • Reproducibility and auditability: keeps notes of each triage step for knowledge sharing.
  • Use Case: When facing compiler errors, test failures, or unexpected runtime behavior, follow the seven-step process to isolate and fix the issue.

Quick Start

Describe the error you see, locate the exact failure point, and follow the seven-step triage to test one targeted fix at a time.

Frequently Asked Questions about self-debugging

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

FAQPage Schema
What is a deterministic debugging workflow for runtime errors?

Stepwise error triage involves reading compiler messages, locating the exact failing file and line, viewing surrounding context, and forming a single hypothesis to avoid guesswork during troubleshooting runtime exceptions and test failures.

How do I diagnose and fix TypeScript or Python runtime exceptions?

To diagnose TypeScript or Python runtime exceptions, follow a seven-step triage process: read the error, locate the file and line, apply one targeted change, and re-test to confirm the impact and ensure reproducibility.

Does this evidence-based debugging approach work for both compiler errors and test failures?

Yes, this evidence-based debugging approach works for compiler errors, test failures, and unexpected runtime behavior across TypeScript, JavaScript, and Python projects by enforcing structured triage and single targeted changes per iteration.

What is the best way to troubleshoot code errors without guesswork?

The best way to troubleshoot code errors without guesswork is using an evidence-based playbook that requires structured triage steps, precise file and line context, and a single targeted change per iteration to ensure deterministic results.

Can I use this triage process for multi-language projects spanning Python and JavaScript?

Yes, you can use this triage process for multi-language projects spanning Python, JavaScript, and TypeScript because it focuses on universal evidence-based debugging mechanics rather than language-specific tooling, ensuring consistent error diagnosis across different runtimes.