skills.rest
jarredkenny
jarredkennyCOMMUNITY
Explore all skills by this author →
Website𝕏@jarredkennyGitHub

systematic-debugging

Trace software failures through a Phase 1-4 workflow with diagnostic instrumentation.

19|4|Updated Feb 1, 2026
Search Tags:#debugging#investigation#systematic#traceability#root-cause#software-engineering
One-click install
npx skills add https://github.com/jarredkenny/agency-ai --skill systematic-debugging-jarredkenny
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/jarredkenny/agency-ai/tree/main/roles/orchestrator/skills/systematic-debugging
Command: npx skills add https://github.com/jarredkenny/agency-ai --skill systematic-debugging-jarredkenny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging to identify and resolve software issues by tracing root causes rather than applying symptoms fixes.

Core Features & Use Cases

  • Phase-driven analysis: Guides users through Phase 1-4 to uncover the true cause of failures.
  • Diagnostic emphasis: Encourages error-message analysis, reproducibility checks, and evidence collection.
  • Use Case: When a bug appears in production, use this skill to methodically trace inputs, calls, and state changes to the root cause before patching.

Quick Start

Follow the Phase 1 steps first: reproduce, log errors, and gather evidence; then follow Phase 2-4 as described in the technique docs.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
How do I systematically debug software issues to find the root cause?▼

Systematic debugging traces root causes through a Phase 1-4 workflow. You reproduce failures, analyze error messages, gather diagnostic evidence, and methodically trace inputs and state changes to uncover the true origin before patching.

What is the best way to investigate production bugs without applying symptom fixes?▼

Root-cause debugging enforces evidence collection over symptom patching. By methodically tracing inputs, calls, and state changes through diagnostic instrumentation, you uncover the actual failure origin across a structured four-phase workflow.

How do I start debugging test failures and performance problems methodically?▼

Start debugging test failures and performance problems with Phase 1: reproduce the issue, log errors, and gather diagnostic evidence. Then proceed through Phases 2-4 to methodically uncover the underlying root cause.

Does systematic root-cause analysis work for integration faults and complex software failures?▼

Systematic root-cause analysis applies to integration faults, test failures, production bugs, and performance problems. It uses diagnostic instrumentation and evidence gathering to methodically uncover root causes across these diverse software failure types.

Why should I use a phase-driven debugging workflow instead of patching symptoms directly?▼

A phase-driven debugging workflow enforces traceability and evidence gathering, ensuring you resolve the true root cause rather than applying temporary symptom fixes that often lead to recurring software issues.

Related Skills

Explore More Software Engineering Skills→
x-TheFoxx-TheFox

systematic-debugging

Enforce root-cause analysis before fixes using a four-phase debugging process.

Community
Advanced
dakshrawat298-gifdakshrawat298-gif

security-fix-review

Review security patches for root-cause coverage and bypass risks.

Community
Intermediate
CUexterCUexter
2

systematic-debugging

Identify root causes of bugs through four structured debugging phases.

Community
Advanced
kk20300113-pngkk20300113-png

systematic-debugging

Investigate root causes through a 4-phase debugging workflow.

Community
Advanced