skills.rest
zxyycom
zxyycomCOMMUNITY
Explore all skills by this author →
GitHub

debugging-and-error-recovery

Diagnose and fix test, build, and runtime failures using structured root-cause debugging.

Updated Jun 4, 2026
Search Tags:#debugging#triage#reproducibility#root-cause#evidence-record#boundary-mapping
One-click install
npx skills add https://github.com/zxyycom/docnav --skill debugging-and-error-recovery-zxyycom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-and-error-recovery
Source: https://github.com/zxyycom/docnav/tree/main/.codex/skills/debugging-and-error-recovery
Command: npx skills add https://github.com/zxyycom/docnav --skill debugging-and-error-recovery-zxyycom

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides a structured approach to diagnose failures by root-cause debugging, reducing triage time and preventing guesswork across tests, builds, and runtime behavior.

Core Features & Use Cases

  • Structured triage workflow: reproduce, localize, isolate, fix, verification.
  • Evidence recording: maintain an Evidence Record with Observed, Expected, Reproduce, Boundary, and Fix fields.
  • Boundary-centric debugging: map observed failures to Parser/Domain, CLI/API, Subprocess/Bridge, Identifier/Read path, and Output modes boundaries.
  • Real-world use: cut incident response time for CI failures, flaky tests, and deployment issues.

Quick Start

向 AI 提出一个失败场景的最小可复现步骤，并要求它按结构化 root-cause 调试流程进行诊断与修复。

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 test failures and build breaks using root-cause analysis?▼

Debug test failures and build breaks using structured root-cause analysis to reproduce, localize, isolate, fix, and verify failures, reducing triage time and preventing guesswork across tests, builds, and runtime behavior.

What is the best way to triage flaky tests and CI failures?▼

Triage flaky tests and CI failures by mapping observed failures to Parser, CLI, or Subprocess boundaries, maintaining an Evidence Record, and creating minimal reproductions for targeted verification.

How do I fix bridge or stdio JSON failures in my runtime environment?▼

Fix bridge or stdio JSON failures by following stepwise boundary localization that isolates the subprocess or bridge issue, records the evidence, and applies a targeted verification fix.

Does this structured debugging approach work for schema and output-mode mismatches?▼

Yes, structured debugging works for schema and output-mode mismatches by mapping observable behavior failures to specific boundaries and verifying the fix within a defined ownership scope.

What should I prepare to start diagnosing failures with structured root-cause debugging?▼

To start diagnosing failures, prepare a minimal reproducible step sequence of the failure scenario and request a structured root-cause debugging workflow to diagnose and fix it.

Related Skills

Explore More Software Engineering Skills→
hujianbesthujianbest
1

hf-hotfix

Analyzes root cause and prepares a handoff to hf-test-driven-dev.

Community
Advanced
ydnikolaevydnikolaev
8

debugger

Debug runtime errors and failing tests with a seven-step workflow.

Community
Basic
brolagbrolag
11

debugging

Diagnoses root causes of software bugs using a four-phase OBSERVE-HYPOTHESIZE-TEST-FIX workflow.

Community
Advanced
JeremyDev87JeremyDev87
31

error-analysis

Classify errors, interpret stack traces, and plan remediation steps.

Community
Advanced