debugging-and-error-recovery

Diagnose and fix root causes of failing tests, broken builds, and runtime errors systematically.

Updated May 27, 2026
One-click install
npx skills add https://github.com/Rkaaaa404/cyberhack-SYDT --skill debugging-and-error-recovery-rkaaaa404
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-and-error-recovery
Source: https://github.com/Rkaaaa404/cyberhack-SYDT/tree/main/.agents/skills/debugging-and-error-recovery
Command: npx skills add https://github.com/Rkaaaa404/cyberhack-SYDT --skill debugging-and-error-recovery-rkaaaa404

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, wasting hours and letting errors compound. This Skill enforces a structured triage process that stops feature work, preserves evidence, and drives the fix to the actual root cause. ## Core Features & Use Cases - Structured Triage Checklist: Six-step workflow covering reproduce, localize, reduce, fix root cause, guard against recurrence, and verify end-to-end. - Layer-Based Fault Localization: Decision trees for narrowing failures across UI, API, database, build tooling, external services, and DaaS backends, plus git bisect guidance for regression bugs. - DaaS and Next.js Debugging Guides: Pre-mapped problem-to-root-cause tables for common DaaS issues (CORS, RBAC, hooks, permissions) and Next.js build failures (type, import, config, dependency errors). - Use Case: A QC review page shows an empty collection list. Instead of adding a fallback empty array, the Skill guides you to trace the failure to a DaaS CORS wildcard misconfiguration, fix the origins, and add a regression test. ## Quick Start Ask the AI to systematically debug the failing test or broken build by reproducing the error, localizing the failing layer, and fixing 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 (UI, API, database, build, or test itself), reduce to a minimal failing case, and fix the root cause. Finish by adding a regression test that fails without the fix and passes with it.

How to find which commit introduced a regression bug?▼

Use git bisect: mark the current commit as bad, mark a known-good commit, and run git bisect run with your test command. Git automatically binary-searches the commit history to identify the exact change that broke the behavior.

Why does my Next.js build fail with import errors?▼

Import errors usually mean the module does not exist, exports do not match, or paths are wrong. For scoped packages like @buildpad or @mantine, verify the package version in package.json and reinstall or run the relevant CLI fix.

Why is my DaaS collection list showing no data?▼

Empty collection data commonly stems from CORS wildcard settings combined with credentials, missing read permissions in RBAC, or expired auth tokens. Check CORS origins, permissions, and the auth proxy flow rather than patching the UI with fallback values.

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

No. Flaky tests often mask real bugs, and skipping them lets errors compound. Investigate the flakiness source, fix the test or the underlying race condition, and only resume feature work after the suite passes reliably.