skills.rest
LonelyTraderBay
LonelyTraderBayCOMMUNITY
Explore all skills by this author →
GitHub

debugging-and-error-recovery

Diagnose test failures, build errors, and runtime bugs through structured root-cause triage.

Updated May 19, 2026
Search Tags:#debugging#root cause analysis#flutter#git bisect#test failure#regression test#error triage
One-click install
npx skills add https://github.com/LonelyTraderBay/vittrade-flutter --skill debugging-and-error-recovery-lonelytraderbay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-and-error-recovery
Source: https://github.com/LonelyTraderBay/vittrade-flutter/tree/main/.agents/skills/debugging-and-error-recovery
Command: npx skills add https://github.com/LonelyTraderBay/vittrade-flutter --skill debugging-and-error-recovery-lonelytraderbay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When tests fail, builds break, or runtime behavior diverges from expectations, developers often guess at fixes or patch symptoms instead of root causes. This Skill enforces a systematic triage process that preserves evidence, localizes the failure, and verifies the fix with regression tests. ## Core Features & Use Cases - Structured Triage Checklist: A six-step workflow covering reproduce, localize, reduce, root-cause fix, regression guard, and end-to-end verification. - Error-Specific Decision Trees: Dedicated triage paths for test failures, build failures, and runtime errors, plus bisection with git for regression bugs. - Escalation Guardrails: After three failed fix attempts across different layers, the process stops patching and escalates to a scoped refactor, revert, or handoff. - Use Case: A Flutter widget test fails after a Riverpod provider change. Follow the checklist to reproduce the failure, trace it through the provider to the repository mock, fix the source, and add a regression test that fails without the fix. ## Quick Start Ask the agent to debug the failing test or broken build using the systematic triage checklist and report the root cause with a regression test.

Frequently Asked Questions about debugging-and-error-recovery

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

FAQPage Schema
How do I debug a failing test systematically?▼

Reproduce the failure reliably first, then localize which layer fails, reduce to a minimal failing case, and fix the root cause rather than the symptom. Finish by adding a regression test that fails without the fix and verifying the full suite passes.

How to find which commit introduced a bug?▼

Use git bisect: mark the current commit as bad and a known working commit as good, then let git checkout midpoint commits while you run the failing test at each step. You can automate it with git bisect run followed by your test command.

What should I do when a bug is not reproducible?▼

Classify it as timing-dependent, environment-dependent, state-dependent, or truly random, then apply the matching strategy such as adding timestamps, comparing environments, checking shared state, or adding defensive logging with alerts.

When should I stop patching and escalate a bug fix?▼

Stop after three distinct fix attempts where each failure appears in a different layer, file, or symbol. This pattern indicates architectural coupling, so report the symptom and fixes tried, then choose a scoped refactor, revert, or handoff.

Why is fixing symptoms instead of root causes a problem?▼

Symptom fixes mask the underlying issue and let it resurface elsewhere, such as deduplicating UI data when the API query produces duplicates. Ask why the failure happens until you reach the actual cause, then fix it at the source.

Related Skills

Explore More Software Engineering Skills→
o3-ozonoo3-ozono

ui-test-debugging

Diagnose CI UI test failures by collecting logs and classifying errors.

Community
Advanced
AceCodePtAceCodePt

implement

Implements work from a spec or tickets using TDD, typechecking, and code review.

Community
Intermediate
levanminhduclevanminhduc

Defense-in-Depth Validation

Enforce defense-in-depth validation across API boundaries, business logic, environment guards, and debug instrumentation.

Community
Advanced
catlog22catlog22
511

quality-refactor

Analyze code issues, plan ordered refactor tasks, and apply test-verified changes.

Community
Advanced