skills.rest
mymx2
mymx2COMMUNITY
Explore all skills by this author →
GitHub

debugging-and-error-recovery

Diagnose software defects through systematic reproduction, localization, and verification.

4|Updated Jun 10, 2026
Search Tags:#testing#quality assurance#debugging#root cause analysis#triage#error recovery
One-click install
npx skills add https://github.com/mymx2/foreman --skill debugging-and-error-recovery-mymx2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-and-error-recovery
Source: https://github.com/mymx2/foreman/tree/main/.agents/skills/debugging-and-error-recovery
Command: npx skills add https://github.com/mymx2/foreman --skill debugging-and-error-recovery-mymx2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the inefficiency of guessing during debugging by providing a rigorous, step-by-step framework to isolate, reproduce, and permanently resolve software defects.

Core Features & Use Cases

  • Structured Triage: A standardized process to move from symptom identification to root-cause resolution.
  • Regression Prevention: Guidelines for creating minimal reproduction cases and verification tests to ensure bugs do not return.
  • Use Case: When a test suite fails intermittently, use this skill to apply the triage checklist, perform git bisection, and implement a robust regression test that prevents the issue from recurring in future builds.

Quick Start

Use the debugging and error recovery skill to perform a systematic triage on the current failing test suite.

Frequently Asked Questions about debugging-and-error-recovery

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

FAQPage Schema
What is the best way to debug intermittent test suite failures?▼

Root cause analysis for debugging intermittent test failures involves applying a structured triage checklist and performing git bisection to isolate the defect, followed by implementing a regression test to permanently prevent recurrence.

How do I find the root cause of a runtime bug or build error?▼

Finding the root cause of a runtime bug or build error requires systematically reproducing and localizing the software defect through a structured methodology, ensuring you verify the fix before resolving the issue.

How do I create a regression test to prevent bugs from returning?▼

To create a regression test that prevents bugs from returning, build a minimal reproduction case for the software defect, then write and run verification tests to ensure long-term code stability across the development lifecycle.

What is the stop-the-line rule in software debugging?▼

The stop-the-line rule in software debugging mandates halting development to address failing tests immediately, ensuring rigorous error recovery and preventing intermittent defects from accumulating in the codebase.

Does systematic triage work for all stages of the software development lifecycle?▼

Systematic triage works across the entire software development lifecycle, applying structured root-cause analysis to test failures, build errors, and runtime bugs regardless of the development stage.

Related Skills

Explore More Software Engineering Skills→
thechandanbhagatthechandanbhagat
8

debug

Analyze stack traces and logs to identify root causes and suggest fixes.

Community
Advanced
vinvcnvinvcn
23

debugging-and-error-recovery

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

Community
Advanced
FlexNetOSFlexNetOS

code-research-verify

Verify code-analysis claims against actual source code.

Official
Advanced
KrismithReddy12KrismithReddy12

qa-only

Test web applications in read-only mode and generate structured bug reports.

Community
Intermediate