skills.rest
LaiTszKin
LaiTszKinCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debug

Diagnose and fix bugs by reproducing plausible causes with tests.

4|2|Updated Feb 25, 2026
Search Tags:#automation#workflow#debugging#root-cause#tests#reproduction-tests#code-inspection
One-click install
npx skills add https://github.com/LaiTszKin/apollo-toolkit --skill systematic-debug-laitszkin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debug
Source: https://github.com/LaiTszKin/apollo-toolkit/tree/main/systematic-debug
Command: npx skills add https://github.com/LaiTszKin/apollo-toolkit --skill systematic-debug-laitszkin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging workflow that ensures observed vs expected behavior is verified with reproducible tests before applying fixes.

Core Features & Use Cases

  • Understand and inspect: parse user reports and code behavior to identify plausible root causes.
  • Reproduce with tests: add or extend tests to reproduce every plausible cause.
  • Diagnose and fix: confirm root cause with reproduction evidence and implement minimal fixes.
  • Use cases include bug reports, flaky tests, runtime errors, and intermittent failures across modules and systems.

Quick Start

Describe the issue and request a reproduction-based debugging pass to identify the root cause and a minimal fix.

Frequently Asked Questions about systematic-debug

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

FAQPage Schema
How do I debug flaky tests and intermittent failures across my codebase?▼

Debug flaky tests by following a four-step workflow: understand and inspect the code, reproduce plausible causes with tests, diagnose and confirm the root cause, and fix and validate the behavior.

What is the best way to reproduce runtime errors before applying code fixes?▼

The best way to reproduce runtime errors is to add or extend tests that consistently trigger the plausible root causes, ensuring observed versus expected behavior is verified before implementing any fixes.

How do I systematically diagnose a bug from a user report?▼

To systematically diagnose a bug, parse the user report and inspect the code to identify plausible root causes, then create reproduction tests to confirm the exact issue before applying a minimal fix.

Does this debugging workflow require any specific testing frameworks or dependencies?▼

No specific testing frameworks or dependencies are required; the workflow is applicable across codebases to diagnose bug reports, runtime errors, and intermittent failures by using reproducible tests.

Why should I write reproduction tests before fixing a bug?▼

Writing reproduction tests before fixing a bug ensures the observed versus expected behavior is verified, confirms the plausible root cause with evidence, and validates that the minimal fix resolves the issue.

Can I use this systematic debugging approach for intermittent failures across different modules?▼

Yes, this systematic debugging approach is applicable to intermittent failures across modules and systems, enforcing a workflow of inspection, reproduction, diagnosis, and validation to resolve issues.

Related Skills

Explore More Software Engineering Skills→
i3ringiti3ringit
3

bug-reproduction-validator

Reproduces reported issues and validates whether they are genuine bugs.

Community
Basic
Smooth-OperationSmooth-Operation

systematic-debugging

Diagnose software bugs with a five-step reproduce, isolate, identify, fix, and verify workflow.

Official
Basic
tianjianjiangtianjianjiang
1

smith-playwright

Monitor Playwright test failures and classify root causes from HTML reports.

Community
Advanced
ydnikolaevydnikolaev
8

debugger

Debug runtime errors and failing tests with a seven-step workflow.

Community
Basic