skills.rest
cautiouskurns
cautiouskurnsCOMMUNITY
Explore all skills by this author →
GitHub

error-debugger

Extract error details from screenshots and trace root causes.

Updated Aug 23, 2026
Search Tags:#debugging#diagnostics#godot#code-analysis#root-cause#stack-trace#error-screenshots
One-click install
npx skills add https://github.com/cautiouskurns/Blood-and-Gold --skill error-debugger-cautiouskurns
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: error-debugger
Source: https://github.com/cautiouskurns/Blood-and-Gold/tree/main/.claude/skills/error-debugger
Command: npx skills add https://github.com/cautiouskurns/Blood-and-Gold --skill error-debugger-cautiouskurns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users diagnose and fix errors shown in screenshots by performing deep analysis that identifies the immediate issue and its root causes, reducing debugging cycles.

Core Features & Use Cases

  • Error extraction and classification: Parses visible error messages, stack traces, and context to determine severity.
  • Root-cause tracing: Maps the failure to its source and suggests targeted fixes.
  • Proactive risk identification: Reveals related code paths that may introduce similar issues.

Quick Start

Provide an error screenshot and say "debug this" to start the diagnostic workflow and generate a fix plan.

Frequently Asked Questions about error-debugger

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

FAQPage Schema
How do I diagnose and fix errors from a screenshot?▼

To diagnose and fix errors from a screenshot, you provide the image and say "debug this". The tool extracts visible error messages and stack traces, reads surrounding code context, and proposes targeted fixes.

Can I use this to analyze a crash log and stack trace across projects?▼

Yes, you can analyze a crash log and stack trace across projects. The workflow maps the failure to its source for root-cause tracing and suggests deterministic fixes for the identified issue.

What is the best way to trace the root cause of a Godot error?▼

The best way to trace the root cause of a Godot error is providing the error screenshot or log. The diagnostic workflow classifies the error severity and maps the failure to its source code path.

Does this debugging tool identify related code paths that might cause similar issues?▼

Yes, the debugging tool performs proactive risk identification. After extracting error details and tracing the root cause, it reveals related code paths that may introduce similar issues in the future.

How do I start the diagnostic workflow for code analysis?▼

You start the diagnostic workflow for code analysis by providing an error screenshot and saying "debug this". This triggers the scripted process to extract error details and generate a fix plan.

Related Skills

Explore More Software Engineering Skills→
msrivmsriv

mobile-debug-doctor

Diagnose Android and iOS crashes from logcat, ANR traces, and Xcode reports.

Community
Advanced
tomguntomgun

fixing-bugs

Reproduce bugs with regression tests and apply minimal root-cause fixes.

Community
Intermediate
nguyenphpnguyenphp
41

lint-and-validate

Run linters, type checkers, and security audits across Node.js and Python projects.

Community
Intermediate
ArabelaTsoArabelaTso
142

abstract-trace-summarizer

Summarize program execution traces and behavior using abstract interpretation.

Community
Advanced