skills.rest
camilooscargbaptista
camilooscargbaptistaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Diagnose software defects using a step-by-step scientific debugging methodology.

7|Updated Mar 19, 2026
Search Tags:#debugging#troubleshooting#observability#root-cause#bisect#memory-leak#incident-response
One-click install
npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill systematic-debugging-camilooscargbaptista
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/camilooscargbaptista/cto-toolkit/tree/main/systematic-debugging
Command: npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill systematic-debugging-camilooscargbaptista

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined, evidence-driven process to diagnose, localize, and fix software defects across stacks and environments, preventing wasted time spent on guesses and unfocused changes.

Core Features & Use Cases

  • Structured scientific workflow: follow observe → hypothesize → predict → test → conclude to turn symptoms into reproducible fixes.
  • Narrowing and isolation techniques: bisect execution paths, use git bisect, isolate data inputs, and apply binary search strategies to find the exact failing code or condition.
  • Production-safe investigation: guidance for read-only queries, distributed tracing correlation, feature-flag driven canaries, and safe debugging practices when reproducing locally is impossible. Use case: Investigate an intermittent production crash by collecting precise logs and traces, forming ranked hypotheses, running targeted experiments (e.g., git bisect or scoped test runs), and recommending a minimal tested fix.

Quick Start

Ask the systematic-debugging skill to perform a structured investigation for the failing endpoint: gather logs and traces, list hypotheses, run targeted tests or git bisect as needed, and propose the minimal verified fix.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is the best way to debug an intermittent production crash?▼

For intermittent flakiness and CI failures, systematic debugging narrows down execution paths by applying binary search strategies, isolating data inputs, and running scoped test cases to pinpoint the exact failing condition.

How do I find a memory leak using a scientific debugging methodology?▼

To find a memory leak using scientific debugging, you gather observability traces and error logs, form ranked hypotheses about the leak source, and run isolated test cases to validate the root cause before applying a fix.

Can I use git bisect to localize software defects in distributed systems?▼

Yes, git bisect localizes software defects by binary searching source history to identify the exact commit introducing the error, which is especially useful when combined with distributed tracing correlation.

How do I safely investigate distributed system inconsistencies when local reproduction is impossible?▼

When local reproduction is impossible, production-safe investigation involves running read-only queries, correlating distributed traces, and using feature-flag driven canaries to observe system behavior without risking further instability.

What do I need to start troubleshooting flaky tests methodically?▼

To start troubleshooting flaky tests methodically, you need clear reproduction steps or observability traces, access to error logs and source history, and the ability to run targeted experiments like isolated test cases.

Why should I use a structured workflow instead of guessing fixes for CI failures?▼

Using a structured workflow for CI failures prevents wasted time on unfocused changes by enforcing an evidence-driven process that turns symptoms into reproducible, verified fixes.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
AlejandroFiginiAlejandroFigini

test-driven-development

Write failing tests first and run red-green-refactor cycles for software changes.

Community
Intermediate
bugrabilgebugrabilge
10

devops-troubleshooter

Diagnose production outages through log analysis and distributed tracing.

Community
Advanced
hung-phanhung-phan

profiling

Identify performance bottlenecks in production systems using profiling tools.

Community
Advanced