skills.rest
ankaboot-source
ankaboot-sourceOFFICIAL
Explore all skills by this author →
WebsiteGitHub

debugging-and-error-recovery

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

2|Updated Jul 25, 2026
Search Tags:#debugging#troubleshooting#root cause analysis#git bisect#test failure#regression test#error triage
One-click install
npx skills add https://github.com/ankaboot-source/boucle --skill debugging-and-error-recovery-ankaboot-source
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-and-error-recovery
Source: https://github.com/ankaboot-source/boucle/tree/main/.jcode/skills/debugging-and-error-recovery
Command: npx skills add https://github.com/ankaboot-source/boucle --skill debugging-and-error-recovery-ankaboot-source

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When tests fail, builds break, or runtime behavior goes wrong, developers often guess at fixes or patch symptoms instead of root causes, wasting hours and letting bugs compound. This Skill enforces a disciplined stop-the-line workflow that preserves evidence, reproduces the failure, and fixes the actual cause. ## Core Features & Use Cases - Six-Step Triage Checklist: Reproduce, localize, reduce, fix the root cause, guard with a regression test, and verify end-to-end. - Error-Specific Decision Trees: Structured triage paths for test failures, build failures, and runtime errors, including git bisect guidance for regression bugs. - Non-Reproducible Bug Strategies: Systematic approaches for timing-dependent, environment-dependent, and state-dependent failures. - Use Case: A CI test starts failing after a refactor. Instead of guessing, you follow the checklist: reproduce it in isolation, bisect to the offending commit, reduce to a minimal case, fix the underlying query bug, and add a regression test that fails without the fix. ## Quick Start Use the debugging-and-error-recovery skill to triage this failing test and find its root cause before fixing anything.

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?▼

Follow a six-step triage: reproduce the failure reliably, localize which layer fails, reduce to a minimal case, fix the root cause rather than the symptom, add a regression test, then verify the full suite and build pass. Never skip reproduction to guess at fixes.

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 git checks out midpoint commits for testing. You can automate it with git bisect run followed by your focused test command.

What should I do when a bug cannot be reproduced?▼

Classify it as timing-dependent, environment-dependent, or state-dependent. Add timestamps and artificial delays for race conditions, compare environments and data for environment issues, and check for leaked shared state between tests or requests.

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

Symptom fixes mask the underlying defect, which resurfaces elsewhere and compounds with later changes. Ask why the failure happens until you reach the actual cause, such as fixing a duplicating JOIN query rather than deduplicating in the UI.

Should I skip a flaky test to keep working on features?▼

No. Flaky tests mask real bugs and skipping them lets errors compound into later work. Investigate timing issues, order dependence, or external dependencies, and fix the flakiness or understand why it is intermittent before resuming.

Related Skills

Explore More Software Engineering Skills→
civitas-cerebrumcivitas-cerebrum
5

failure-diagnosis

Diagnose failing Playwright tests through evidence-based triage of traces, screenshots, and console logs.

Official
Advanced
Chorus-AIDLCChorus-AIDLC
1.1k

pr-workflow

Automate pull request workflows with git and the GitHub CLI.

Official
Intermediate
prefactordevprefactordev
3

instrument-existing-agent-with-prefactor-sdk

Instrument existing agents with Prefactor to trace run, LLM, and tool boundaries.

Official
Advanced
sentenzsentenz
3

go-fuzz-testing

Automate fuzz testing of Go packages with native fuzzing engine.

Community
Advanced