debugging-and-error-recovery

Diagnose software failures through structured triage and root-cause analysis.

Updated Jun 21, 2026
One-click install
npx skills add https://github.com/Huytutu/KRONOS --skill debugging-and-error-recovery-huytutu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging-and-error-recovery
Source: https://github.com/Huytutu/KRONOS/tree/main/.agents/skills/debugging-and-error-recovery
Command: npx skills add https://github.com/Huytutu/KRONOS --skill debugging-and-error-recovery-huytutu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates wasted time and compounded errors from unguided, guess-based debugging when tests fail, builds break, or unexpected runtime issues occur, ensuring you fix the actual root cause instead of temporary symptoms.

Core Features & Use Cases

  • Structured Triage Workflow: A 6-step repeatable process (reproduce, localize, reduce, fix root cause, guard against recurrence, verify) that works for all failure types from local test errors to production incidents.
  • Error-Specific Decision Trees: Pre-built triage patterns for test failures, build errors, and runtime bugs to quickly narrow down the source of the issue.
  • Recurrence Prevention: Guidance to write regression tests and add guardrails so fixed bugs never resurface.
  • Use Case: When a CI pipeline fails after a code change, use this Skill to bisect to the offending commit, reduce the issue to a minimal reproduction, fix the underlying bug, and add a test to catch it if it happens again.

Quick Start

Use the debugging-and-error-recovery skill to systematically diagnose and fix the failing end-to-end test for the user checkout flow.

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 fix failing end-to-end tests without guesswork?

Resolve failing end-to-end tests by applying a structured triage workflow: reproduce the failure, localize the fault, reduce to a minimal reproduction, fix the root cause, and add regression tests to prevent recurrence.

What is the best way to debug a CI pipeline build error after a code change?

Debug a CI pipeline build error by using error-specific decision trees to bisect to the offending commit, reduce the issue to a minimal reproduction, fix the underlying bug, and add a guardrail test to catch it if it happens again.

How do I find the root cause of a runtime bug in production?

Find the root cause of a runtime bug by systematically matching error-specific patterns to narrow down the source, then applying a repeatable triage process to safely fix the underlying issue instead of treating temporary symptoms.

How do I prevent a fixed bug from resurfacing in my software?

Prevent a fixed bug from resurfacing by implementing recurrence prevention guidance, which involves writing regression tests and adding guardrails immediately after fixing the root cause to verify the system behavior matches expectations.

Does structured troubleshooting work for local test failures and live production incidents?

Structured troubleshooting works for all development and production scenarios where system behavior does not match expectations, applying a repeatable 6-step process to resolve both local test failures and live production incidents.