skills.rest
graniet
granietCOMMUNITY
Explore all skills by this author →
Website𝕏@graniet75GitHub

systematic-debugging

Investigate technical issues through a structured 4-phase root cause workflow.

247|22|Updated Dec 11, 2024
Search Tags:#debugging#problem solving#troubleshooting#software development#root cause analysis#bug fixing#test failure
One-click install
npx skills add https://github.com/graniet/kheish --skill systematic-debugging-graniet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/graniet/kheish/tree/main/skills/software-development/systematic-debugging
Command: npx skills add https://github.com/graniet/kheish --skill systematic-debugging-graniet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Random, unplanned debugging wastes hours of engineering time, introduces new bugs, and fails to address the true root cause of technical issues, leading to recurring problems and unstable systems.

Core Features & Use Cases

  • 4-Phase Structured Process: Guides users through root cause investigation, pattern analysis, hypothesis testing, and verified implementation to ensure fixes are permanent and don't create new issues.
  • Built-in Guardrails: Enforces a strict "no fixes without root cause" rule, with clear red flags to stop unproductive debugging and prompts to question system architecture after 3 failed fix attempts.
  • Tool & Skill Integration: Works seamlessly with Kheish's investigation tools (file search, terminal, web research) and pairs with the test-driven-development skill to create regression tests that prevent future bugs.
  • Use Case: When a production test suite starts failing unexpectedly after a dependency update, this Skill helps you reproduce the issue, trace the data flow to find the root cause, and implement a verified fix without introducing new bugs.

Quick Start

Use the systematic-debugging skill to investigate the failing user authentication test suite and identify the root cause of the login validation errors.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
How do I find the root cause of a test failure without guessing?▼

Finding the root cause of a test failure requires a structured 4-phase investigation process: root cause identification, pattern analysis, hypothesis testing, and verified implementation. This systematic approach replaces guess-based debugging to ensure fixes are permanent and do not introduce new bugs.

What is the best way to stop recurring production bugs after a dependency update?▼

The best way to stop recurring production bugs is to apply a strict root cause investigation workflow with built-in guardrails. This enforces a 'no fixes without root cause' rule and prompts you to question system architecture after 3 failed fix attempts, preventing unstable systems and recurring issues.

How do I debug integration errors and build failures systematically?▼

Debug integration errors and build failures systematically by tracing data flow and analyzing patterns through a 4-phase process. This workflow integrates with development tools to gather evidence, ensuring your verified implementation addresses the actual technical issue rather than symptoms.

Can I use systematic debugging with test-driven development practices?▼

Yes, you can use systematic debugging with test-driven development. The 4-phase investigation workflow pairs directly with TDD practices to create regression tests after identifying a root cause, preventing future bugs and ensuring your verified fix does not introduce new issues.

When should I question system architecture during bug fixing?▼

You should question system architecture during bug fixing when you experience 3 failed fix attempts. The systematic debugging process includes built-in guardrails that flag this as a red flag to stop unproductive debugging and prompt deeper architectural investigation into the root cause.

Related Skills

Explore More Software Engineering Skills→
AissenLiuAissenLiu

systematic-debugging

Solves bugs via a four-phase root-cause investigation workflow with diagnostic tools.

Community
Advanced
DYAI2025DYAI2025

regression-test-generator

Generate Arrange-Act-Assert regression tests for Jest, Vitest, pytest, or Playwright.

Community
Intermediate
LuminairPrimeLuminairPrime
1

investigate

Investigate software bugs through root-cause analysis and hypothesis testing.

Community
Advanced
flybirdxxflybirdxx

systematic-debugging

Implement a 4-phase debugging process for root cause analysis.

Community
Advanced