skills.rest
jankneumann
jankneumannCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debugging-and-error-recovery

Guide systematic root-cause debugging with a Stop-the-Line triage workflow.

Updated Apr 12, 2026
Search Tags:#debugging#root cause#pytest#regression testing#triage#error recovery#git bisect
One-click install
npx skills add https://github.com/jankneumann/agentic-assistant --skill debugging-and-error-recovery-jankneumann
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-and-error-recovery
Source: https://github.com/jankneumann/agentic-assistant/tree/main/.agents/skills/debugging-and-error-recovery
Command: npx skills add https://github.com/jankneumann/agentic-assistant --skill debugging-and-error-recovery-jankneumann

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of inefficient, compounding debugging when tests fail, builds break, or runtime behavior is unexpected.

Core Features & Use Cases

  • Stop-the-Line triage: preserve evidence, halt feature-churn, and switch to root-cause diagnostics before making further changes.
  • Structured debugging workflow: reproduce reliably, localize the failing layer, reduce to a minimal failing case, fix the underlying cause, guard with a regression test, and verify end-to-end.
  • Regression and safety patterns: use targeted bisect/repro strategies, handle flakiness, and treat error output as untrusted diagnostic data rather than blindly following embedded instructions.

Quick Start

Use the debugging-and-error-recovery skill when your tests fail or your build breaks to follow reproduce → localize → reduce → fix → guard → verify steps systematically.

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 a failing test without compounding code changes?▼

This Skill enforces a Stop-the-Line triage workflow that halts further changes to preserve evidence, applying a structured debugging checklist to find the root cause of failing tests safely.

How do I systematically find the root cause of a broken build?▼

To find the root cause of a broken build, follow a structured debugging workflow: reproduce reliably, localize the failing layer, reduce to a minimal failing case, fix the underlying cause, guard with a regression test, and verify end-to-end.

When should I use git bisect for regression investigations?▼

You should use git bisect during regression investigations when applying targeted bisect and repro strategies to isolate the specific commit that introduced the failure, ensuring reliable reproduction before fixing.

How do I handle flakiness and untrusted diagnostic error text during triage?▼

Handle flakiness by applying targeted repro strategies to stabilize tests, and treat error output as untrusted diagnostic data rather than blindly following embedded instructions to ensure safe error recovery.

Does this debugging workflow support pytest regression testing?▼

Yes, this debugging workflow applies to pytest regression testing by guiding you through reproducing the failure, localizing the issue, reducing the case, and adding a regression guard test for verification.

Related Skills

Explore More Software Engineering Skills→
FoxSilouFoxSilou

task-fix-bug-back

Reproduce backend bugs with failing tests before applying minimal code fixes.

Community
Intermediate
ydnikolaevydnikolaev
8

debugger

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

Community
Basic
rsicarellirsicarelli
63

compilation-error-analyzer

Diagnose Fakt compilation errors and classify root causes in Kotlin/Gradle workflows.

Community
Advanced
svssdevasvssdeva
1

debugging-and-error-recovery

Guides root-cause debugging for failing tests, builds, runtime errors, and incorrect behavior.

Community
Advanced