Diagnose failing tests and propose minimal fixes with a structured mission-report.
npx skills add https://github.com/MathieuDoyon/mission --skill mission-debug
Please help me install this Agent Skill. Skill: mission-debug Source: https://github.com/MathieuDoyon/mission/tree/main/.claude/skills/mission-debug Command: npx skills add https://github.com/MathieuDoyon/mission --skill mission-debug
mission-debug helps you understand why a failing test or unexpected behavior is happening, so you can confidently move forward instead of guessing at fixes.
Ask Claude to run mission-debug for your failing behavior and return a mission-report describing the most likely root cause and a minimal proposed change.
High-intent search queries and answers about installing and using this skill.
Debug a failing test systematically by reproducing the failure, testing one falsifiable hypothesis at a time, and isolating the exact file and line. This produces a structured report with the root-cause location and a minimal proposed fix you can verify.
Root cause analysis for debugging is the process of recreating a failure, capturing observed versus expected outcomes, and isolating the specific code change responsible. You need it when a failing test or unexpected output blocks progress and guessing is inefficient.
The best way to debug a regression is hypothesis-driven isolation: recreate the failure, test one possible cause at a time using the minimum targeted read or experiment, then document the root-cause location and propose the smallest fix without applying it.
Create a targeted verification plan by reproducing the original failure, isolating the root-cause location, and defining the minimal set of tests needed to confirm the proposed fix resolves the regression without introducing new issues.
Yes, systematic debugging applies to any unexpected output. It recreates the behavior, captures observed versus expected outcomes, isolates the likely cause through targeted experiments, and proposes the smallest fix with a verification plan.
Minimal-change debugging isolates a single localizable root cause and proposes the smallest fix, so it may not fully address complex regressions spanning multiple systems or non-localized architectural issues that require broader changes.
tmdgusyaEnforce a reproduce-first, root-cause-first debugging workflow with evidence and verification.
dmae97Guide bug resolution from reproduction evidence to root-cause analysis and minimal code changes.
DaddyElonMusk69Enforce test-first development with failing tests, minimal code, and regression checks.
nahisahoDiagnose software bugs through investigation, reproduction, and root-cause analysis.
