systematic-debugging
Root-cause-first debugging methodology. Use when encountering any bug, test failure, or unexpected behavior BEFORE proposing fixes. Prevents random fix attempts that waste time and create new bugs.
Why use this skill?
Master root-cause-first debugging with the systematic-debugging skill. Prevent random fix attempts and improve code reliability with this structured 4-phase methodology.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/kjaylee/systematic-debuggingWhat This Skill Does
The systematic-debugging skill is a rigorous, root-cause-first framework designed to prevent the common pitfall of 'guess-and-check' coding. Instead of allowing the AI to propose random patches that often introduce regression bugs, this skill forces a disciplined, four-phase investigation. It mandates thorough error log analysis, precise reproduction steps, data flow tracing, and the creation of failing test cases before any code is modified. By adhering to the 'no fix without root cause' iron rule, the agent minimizes technical debt and increases the reliability of the software under maintenance.
Installation
To integrate this methodology into your OpenClaw environment, execute the following command in your terminal:
clawhub install openclaw/skills/skills/kjaylee/systematic-debugging
Use Cases
- Production Outages: Use when a critical service fails and you need to isolate the fault without causing further instability.
- Heisenbugs: Ideal for bugs that appear inconsistently or depend on complex race conditions where guessing is useless.
- Legacy Code Maintenance: Helps developers understand poorly documented systems by enforcing a structured investigation process.
- Refactoring: When code is fragile, use this skill to ensure you understand exactly what a block of code does before changing its structure.
Example Prompts
- "I am getting a 500 error on the user profile update. Please use systematic-debugging to investigate the source of the crash."
- "The unit tests for the authentication module are failing intermittently. Apply the 4-phase process to trace the root cause."
- "I have a bug where the API response returns an empty array. Don't try to fix it yet; start the systematic-debugging process to find exactly where the data flow is broken."
Tips & Limitations
- Tip: Trust the Phase 4 'Stop' condition. If you fail to fix the issue after three attempts, admit that the architectural assumptions are likely incorrect. Continuing to patch will only exacerbate the issue.
- Tip: Use the table of 'Rationalization' provided in the documentation to identify when you or your agent are cutting corners.
- Limitation: This skill is highly process-heavy. For extremely trivial syntax errors, you may find the full four-phase process slightly overkill, though it remains the safest way to ensure long-term code quality.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-kjaylee-systematic-debugging": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-read, file-write, code-execution
Related Skills
ralph-loop
AI 자율 구현 방법론. 구현/개발/코딩 요청 시 자동 적용. 메인은 마더 서브에이전트를 spawn하고, 마더가 워커들을 관리. specs/ → IMPLEMENTATION_PLAN.md → 1태스크씩 구현 → 2단계 리뷰 → 테스트 → 반복.
game-dev-rust-godot
Game development workflow using Rust+WASM or Godot 4.x for HTML5 games. Use when creating new games, implementing game mechanics, or porting existing games. Follows TDD-based production pipeline v3.1 with asset-first approach. Covers Rust(Macroquad/Bevy), Godot HTML5 Export, asset acquisition, test case writing, and QA automation. Master directive (2026-02-06) - ONLY Rust+WASM or Godot allowed, JS/TS frameworks prohibited.
subagent-dev
Execute implementation plans using fresh subagents per task with two-stage review (spec compliance + code quality). Use when executing multi-task plans with independent work units. Enhances ralph-loop methodology.
stripe-payments
Best practices for Stripe payment integration. Use when implementing payments, subscriptions, checkout flows, or any monetization feature in games or web apps. Covers CheckoutSessions, Payment Element, subscriptions, and Connect.
ui-ux-pro-max
UI/UX design intelligence and implementation guidance for building polished interfaces. Use when the user asks for UI design, UX flows, information architecture, visual style direction, design systems/tokens, component specs, copy/microcopy, accessibility, or to generate/critique/refine frontend UI (HTML/CSS/JS, React, Next.js, Vue, Svelte, Tailwind). Includes workflows for (1) generating new UI layouts and styling, (2) improving existing UI/UX, (3) producing design-system tokens and component guidelines, and (4) turning UX recommendations into concrete code changes.