debug

Converts bug reports into verified fixes with reproducible tests.

12|5|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/ai-pivot/xbot --skill debug-ai-pivot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/ai-pivot/xbot/tree/main/tools/embed_skills/debug
Command: npx skills add https://github.com/ai-pivot/xbot --skill debug-ai-pivot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug turns unclear bug reports into a reproducible, verifiable fix plan so you can stop guessing and confirm correctness.

Core Features & Use Cases

  • Failure clarification: Converts vague reports into observed vs expected behavior, scope, and concrete success criteria.
  • Reproduce first: Drives test-first debugging by adding or updating the smallest failing automated check possible.
  • Fix and verify: Ensures changes are applied only after reproduction exists, then re-runs the reproduction to confirm the fix and checks nearby validations.

Quick Start

Ask the skill to debug a reported issue by requesting: the reproduction steps, expected vs actual behavior, any failing command or test output, and a success criterion for the fix.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I reproduce a bug from a vague crash report?

To reproduce a bug from a vague crash report, you need to clarify the observed versus expected behavior and define concrete success criteria. This approach converts unclear issues into a verifiable fix plan by creating the smallest failing automated check possible to confirm the crash.

What is the best way to fix a regression without introducing new issues?

The best way to fix a regression is to scope changes strictly to the verified cause after creating a failing test. By re-running the reproduction and nearby validations post-fix, you confirm the regression is resolved without introducing new issues.

How do I debug a flaky test in my CI workflow?

To debug a flaky test in your CI workflow, turn the reported issue into a reproducible failure by defining expected behavior and adding a failing automated check. Once the flaky behavior is consistently reproduced, apply fixes and re-run validations to verify correctness.

Does test-first debugging work for incorrect outputs and regressions?

Yes, test-first debugging works for incorrect outputs and regressions by requiring a failing automated check to exist before any code changes are applied. This ensures the incorrect output is reliably reproduced and verified against defined success criteria.

Why does my bug fix require a success criterion before implementation?

Your bug fix requires a success criterion to stop guessing and confirm correctness. Defining expected behavior upfront ensures the fix is scoped to the verified cause and validated by re-running the reproduction test.

What information do I need to provide to investigate a failing behavior?

To investigate a failing behavior, you need to provide reproduction steps, the expected versus actual behavior, any failing command or test output, and a success criterion for the fix. This evidence drives the test-first debugging process.