Verified:GitHub

systematic-debugging

Identify and resolve software bugs through a structured, phase-driven debugging process.

11|Updated May 17, 2026

Search Tags:#debugging #troubleshooting #root-cause-analysis #systematic-process #phase-driven-workflow #data-flow-tracing #tools-integration

Ready to run

npx skills add https://github.com/StarryCod/cogitum --skill systematic-debugging-starrycod

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/StarryCod/cogitum/tree/main/cogitum/data/skills/software-development/systematic-debugging
Command: npx skills add https://github.com/StarryCod/cogitum --skill systematic-debugging-starrycod

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Random fixes waste time and create new bugs. Systematic Debugging provides a disciplined, phase-driven approach to identify root causes before attempting remedies.

Core Features & Use Cases

Phase-driven debugging workflow (Phases 1-4) to systematically investigate issues.
Tooling guidance: use search_files, read_file, terminal, web_search, and delegation for multi-component analysis.
Real-world scenarios include test failures, production bugs, and integration issues where rapid yet reliable root-cause analysis is needed.

Quick Start

Begin by acknowledging the issue, read the error messages, reproduce reliably, and trace data flow using the recommended tools.

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 process for finding software bug root causes?▼

A systematic debugging process identifies software bug root causes through a structured, phase-driven workflow. It emphasizes reliable reproduction, evidence gathering, and data flow tracing across multi-component systems before attempting any remedies.

How do I debug production bugs and test failures across multiple components?▼

Debug production bugs and test failures using a four-phase workflow. You investigate multi-component systems by tracing data flow and gathering evidence with integrated tools like terminal execution, file reading, and web search.

What's the best way to trace data flow when troubleshooting integration issues?▼

The best way to trace data flow during troubleshooting involves reading error messages and reliably reproducing the issue. You then use search and file reading tools to systematically investigate integration issues across components.

Why does random fixing waste time and create new bugs during root-cause analysis?▼

Random fixing wastes time because it attempts remedies before identifying the actual root cause, which often creates new bugs. A disciplined, phase-driven approach ensures you gather evidence and understand the data flow first.

Can I use terminal and web search tools for systematic root-cause investigation?▼

Yes, you can use terminal and web search tools for systematic root-cause investigation. The workflow integrates search_files, read_file, terminal, and web_search to analyze multi-component systems and gather robust evidence.