Diagnose unhandled errors by tracing stack traces and data flow.
npx skills add https://github.com/luisitoys12/luxcode-ai --skill fix-errors-luisitoys12
Please help me install this Agent Skill. Skill: fix-errors Source: https://github.com/luisitoys12/luxcode-ai/tree/main/.agent/skills/fix-errors Command: npx skills add https://github.com/luisitoys12/luxcode-ai --skill fix-errors-luisitoys12
Guidelines for fixing unhandled errors and investigating stack traces. Helps developers trace data flow through call stacks, identify producers of invalid data versus consumers that crash, and enrich error messages while avoiding swallowing errors.
Provide a failing stack trace and a small reproducer to begin diagnosing the error.
High-intent search queries and answers about installing and using this skill.
Trace data flow through the call stack to identify the producer of invalid data versus the consumer that crashes. By analyzing the stack trace, you can pinpoint the exact origin of the unhandled error and remediate it at the source.
The best way to fix error propagation across IPC and API boundaries is to enrich error messages with contextual data rather than masking or swallowing them. This ensures consumers receive detailed fault analysis for faster debugging and stable remediation.
Trace data flow from producer to consumer by analyzing the stack trace to map the journey of invalid data. This isolates the exact producer generating the fault, allowing you to fix the source rather than patching the crashing consumer.
You should avoid swallowing errors during software debugging because it masks the root cause and prevents accurate fault analysis. Enriching error messages with context instead ensures the unhandled error is visible for effective stack-trace diagnosis.
Yes, you can use this for debugging runtime crashes across general software development workflows. It applies to tracing stack traces and error propagation across IPC and API boundaries without requiring specific dependencies or components.
To begin diagnosing a failing stack trace, you need to provide the stack trace itself alongside a small reproducer. This input allows the diagnostic process to trace data flow and identify the error producer effectively.
derHakenTrace data flow and apply a four-phase process to fix root causes.
santanapolDiagnose failing tests, build errors, and runtime issues with structured triage workflows.
salvo-rsCapture request metrics, trace spans, and error contexts for Salvo routes.
VanLAnalyze code diffs for security vulnerabilities, concurrency bugs, and quality issues.
