auto-debugger

Automate end-to-end error investigation and debugging across languages and runtimes.

Updated Jul 10, 2023

Search Tags:#automation #debugging #multi-language #developer-tools #error-analysis #stack-trace #regression-testing

Ready to run

npx skills add https://github.com/iamtatsuki05/dotfiles --skill auto-debugger

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: auto-debugger
Source: https://github.com/iamtatsuki05/dotfiles/tree/main/dotfiles/.agent/skills/auto-debugger
Command: npx skills add https://github.com/iamtatsuki05/dotfiles --skill auto-debugger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auto Debugger autonomously handles errors reported by users: it collects context, traces the source of failures, suggests root causes, and performs safe print debugging to reproduce and diagnose issues across languages and frameworks.

Core Features & Use Cases

Context collection: extracts errors, stack traces, and relevant state from the failure.
Autonomous debugging loop: generates hypotheses, creates validation scripts, runs checks, and iterates until a root cause is identified.
Regression testing: produces regression tests and a repair plan to prevent recurrence across language ecosystems.

Quick Start

Instruct Auto Debugger to autonomously investigate the reported error and return a repair plan and regression tests.

Frequently Asked Questions about auto-debugger

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

FAQPage Schema

How do I automate error investigation and debugging across multiple programming languages?▼

To automate debugging across multiple languages, you need a tool that extracts errors, generates hypotheses, and runs validation scripts. This Skill autonomously executes an end-to-end debugging loop to identify root causes across various runtimes.

What is the best way to generate regression tests from a runtime failure or stack trace?▼

The best way to generate regression tests from a runtime failure is to autonomously trace the source of the exception and inspect the relevant code. This Skill produces regression tests and a repair plan to prevent recurrence across language ecosystems.

Can I use autonomous debugging to reproduce exceptions and test hypotheses for failing tests?▼

Yes, you can use autonomous debugging to reproduce exceptions and test hypotheses for failing tests. The Skill generates validation scripts, executes print-debug scripts, and iterates until a root cause is identified from the provided stack traces.

Does autonomous debugging work without access to source files and error messages?▼

No, autonomous debugging requires access to error messages, stack traces, and relevant source files to function correctly. It also needs the ability to execute print-debug scripts and produce minimal reproductions to accurately diagnose issues.

How do I diagnose a runtime failure when I only have an error message and no clear root cause?▼

To diagnose a runtime failure with only an error message, you need an autonomous debugging loop that gathers context and inspects code. This Skill generates hypotheses, creates validation scripts, and iterates until a root cause is identified.