systematic-debugging

Reproduce, analyze, fix, and verify software bugs with a structured 4-phase framework.

15|1|Updated Dec 4, 2025
One-click install
npx skills add https://github.com/FreePeak/ktme --skill systematic-debugging-freepeak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/FreePeak/ktme/tree/main/.kilo/skills/systematic-debugging
Command: npx skills add https://github.com/FreePeak/ktme --skill systematic-debugging-freepeak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Debugging provides a disciplined, repeatable framework to reproduce, analyze, fix, and verify bugs across software projects.

Core Features & Use Cases

  • Structured 4-phase workflow (Reproduce, Analyze Root Cause, Implement Fix, Verify) to guide debugging from start to finish.
  • Evidence-driven investigation with templates for reproduction steps, findings, and verification to ensure traceability.
  • Safe, minimal changes with guardrails, edge-case handling, and regression checks to prevent new issues.
  • Real-world use cases include debugging intermittent production issues, failing tests, and performance regressions with repeatable outcomes.

Quick Start

Provide a minimal reproduction of the bug and follow the four phases to reproduce, analyze, fix, and verify the issue.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is a systematic debugging workflow for fixing software bugs?

Systematic debugging is a 4-phase workflow to reproduce, analyze root cause, implement fix, and verify bugs. It provides structured templates for evidence collection and rigorous verification to ensure traceable and repeatable outcomes across software projects.

How do I find the root cause of intermittent production issues?

To find the root cause of intermittent production issues, apply a structured debugging framework to reproduce the bug reliably. Use evidence-driven investigation templates to collect precise findings and isolate the root cause fast before implementing any fix.

What is the best way to fix failing tests and performance regressions?

The best way to fix failing tests and performance regressions is applying a 4-phase debugging framework. Reproduce the issue reliably, analyze the root cause, implement a safe minimal fix, and verify with regression checks to prevent new issues.

Does this debugging framework work for any software project?

Yes, this debugging framework works across software projects by design. It uses structured templates for reproduction steps, findings, and verification to guide evidence-driven investigation regardless of the specific platform or codebase.

How do I ensure safe minimal changes when fixing bugs?

To ensure safe minimal changes when fixing bugs, use a structured debugging framework with built-in guardrails. It enforces edge-case handling and regression checks during the implement fix phase to prevent introducing new issues.

Why does fixing a bug often introduce new issues?

Fixing a bug often introduces new issues when changes lack guardrails and regression checks. A systematic debugging framework prevents this by enforcing safe, minimal changes with rigorous verification during the fix and verify phases.