{"id":"37ff655b-a14b-44bc-80c2-c87ce5023573","entityType":"agent","slug":"clawhub-aptratcn-xiaobai-systematic-debugging","name":"Systematic Debugging","canonicalUrl":"https://www.xpersona.co/agent/clawhub-aptratcn-xiaobai-systematic-debugging","canonicalPath":"/agent/clawhub-aptratcn-xiaobai-systematic-debugging","generatedAt":"2026-10-12T18:16:04.977Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-11T22:40:23.143Z","emptyReason":null},"description":"Systematic Debugging - 4-phase root cause process. No guessing, no random fixes. Trace evidence, identify root cause, fix systematically. Skill: Systematic Debugging Owner: aptratcn Summary: Systematic Debugging - 4-phase root cause process. No guessing, no random fixes. Trace evidence, identify root cause, fix systematically. Tags: debugging:2.0.0, latest:2.0.0, root-cause:1.0.0, systematic:1.0.0, troubleshooting:2.0.0 Version history: v2.0.0 | 2026-04-21T09:10:36.260Z | user v2.0: 4-phase framework with real examples v1.0.0 | 2026-04-21T07:11:05.825Z","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 983 downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s17cpfvkz8jmsw8vpgqypg10vh857dxa:xiaobai-systematic-debugging","sourceUrl":"https://clawhub.ai/aptratcn/xiaobai-systematic-debugging","homepage":"https://clawhub.ai/aptratcn/skills/xiaobai-systematic-debugging","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/aptratcn/xiaobai-systematic-debugging","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/aptratcn/skills/xiaobai-systematic-debugging","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":60,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Systematic Debugging - 4-phase root cause process. No guessing, no random fixes. Trace evidence, identify root cause, fix systematically. Skill: Systematic Debu"},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T22:40:23.143Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T22:40:23.143Z","emptyReason":null},"stars":null,"forks":null,"downloads":983,"likes":null,"task":null,"library":null,"packageName":null,"latestVersion":"2.0.0","tractionLabel":"983 downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T22:40:23.130Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T22:40:23.143Z","lastCrawledAt":"2026-10-11T22:40:23.130Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T22:40:23.130Z","lastVerifiedAt":null,"highlights":[{"version":"2.0.0","createdAt":"2026-04-21T09:10:36.260Z","changelog":"v2.0: 4-phase framework with real examples","fileCount":4,"zipByteSize":4223},{"version":"1.0.0","createdAt":"2026-04-21T07:11:05.825Z","changelog":"Initial release: 4-phase root cause debugging process","fileCount":2,"zipByteSize":2739}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17cpfvkz8jmsw8vpgqypg10vh857dxa:xiaobai-systematic-debugging","setupComplexity":"low","setupSteps":["Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-aptratcn-xiaobai-systematic-debugging/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-aptratcn-xiaobai-systematic-debugging/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-aptratcn-xiaobai-systematic-debugging/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-aptratcn-xiaobai-systematic-debugging/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-aptratcn-xiaobai-systematic-debugging/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-aptratcn-xiaobai-systematic-debugging/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-12T18:16:04.977Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-aptratcn-xiaobai-systematic-debugging/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-aptratcn-xiaobai-systematic-debugging/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-aptratcn-xiaobai-systematic-debugging/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-aptratcn-xiaobai-systematic-debugging/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-11T22:40:23.143Z","emptyReason":null},"readme":"Skill: Systematic Debugging\n\nOwner: aptratcn\n\nSummary: Systematic Debugging - 4-phase root cause process. No guessing, no random fixes. Trace evidence, identify root cause, fix systematically.\n\nTags: debugging:2.0.0, latest:2.0.0, root-cause:1.0.0, systematic:1.0.0, troubleshooting:2.0.0\n\nVersion history:\n\nv2.0.0 | 2026-04-21T09:10:36.260Z | user\n\nv2.0: 4-phase framework with real examples\n\nv1.0.0 | 2026-04-21T07:11:05.825Z | user\n\nInitial release: 4-phase root cause debugging process\n\nArchive index:\n\nArchive v2.0.0: 4 files, 4223 bytes\n\nFiles: README.md (1097b), skill-card.md (1868b), SKILL.md (4002b), _meta.json (147b)\n\nFile v2.0.0:SKILL.md\n\n---\nname: systematic-debugging\nversion: 2.0.0\ndescription: 4-phase root cause debugging. Never guess, find the cause. Based on real production debugging methodology. Trigger on: 'bug', 'error', 'not working', 'broken', 'debug', 'fix this'.\nemoji: 🔍\n---\n\n# Systematic Debugging 🔍\n\n4 phases. No guessing. Find root cause.\n\n## The 4 Phases\n\n```\nPhase 1: OBSERVE    → What exactly is wrong? (Gather evidence)\nPhase 2: ISOLATE    → Where does it go wrong? (Narrow scope)\nPhase 3: HYPOTHESIZE → Why does it go wrong? (Form theory)\nPhase 4: VERIFY     → Is it actually fixed? (Prove it)\n```\n\n## Phase 1: OBSERVE (Don't Skip This)\n\n**Before touching any code, answer these:**\n\n```\n□ What is the expected behavior?\n□ What is the actual behavior?\n□ When did it start? (What changed?)\n□ Is it reproducible? (100%? Intermittent?)\n□ What's the exact error message / log output?\n□ What environment? (OS, version, dependencies)\n```\n\n**Common mistake:** Jumping to \"I think it's because...\" without observing first.\n\n**What to do:**\n- Read the actual error (copy-paste, don't paraphrase)\n- Check logs (recent ones first)\n- Reproduce the issue (if possible)\n- Document what you see\n\n## Phase 2: ISOLATE (Narrow the Scope)\n\n**Binary search for the bug:**\n\n```\n1. Is the problem in my code or external?\n   → Comment out my code. Still broken? External.\n\n2. Is it in the input, processing, or output?\n   → Print/log at each stage.\n\n3. Is it in one specific file/function?\n   → Remove files/functions one by one.\n   → Bug disappears? That's where it is.\n\n4. Is it a specific condition?\n   → Test with different inputs.\n   → Pattern emerges? Root cause narrows.\n```\n\n**Techniques:**\n- `git bisect` — Find the commit that introduced the bug\n- Print statements at boundaries\n- Comment out code sections\n- Test with minimal reproduction\n\n## Phase 3: HYPOTHESIZE (Form a Theory)\n\n**Write your hypothesis BEFORE fixing:**\n\n```\nI believe [X] is broken because [Y].\n\nEvidence supporting:\n- [Observation 1]\n- [Observation 2]\n\nEvidence against:\n- [Observation 3]\n\nIf I change [Z], the fix should:\n- Make [test case] pass\n- Not break [other thing]\n```\n\n**Common mistake:** Fixing without understanding. You might \"fix\" the symptom, not the cause.\n\n**Anti-patterns:**\n- ❌ \"Let me try changing this...\" (random fixing)\n- ❌ \"This usually works...\" (cargo cult debugging)\n- ❌ \"It's probably a race condition\" (vague guess)\n\n## Phase 4: VERIFY (Prove It)\n\n**Before claiming \"fixed\":**\n\n```\n□ Original test case now passes\n□ Edge cases tested\n□ No new regressions introduced\n□ Error no longer appears in logs\n□ Fix makes sense given the hypothesis\n```\n\n**Verification checklist:**\n```bash\n# Run the failing test\nnpm test -- --grep \"failing test\"\n# Check logs for errors\ntail -f /var/log/app.log\n# Test edge cases\n[try empty input, huge input, unicode, etc.]\n# Run full test suite\nnpm test\n```\n\n## Real Example\n\n**Bug:** \"User login sometimes fails\"\n\n```\nPhase 1 OBSERVE:\n- Error: \"Invalid token\" (not \"wrong password\")\n- Intermittent (10% of logins)\n- Started after deploying auth-service v2.3\n- Only on mobile, not desktop\n\nPhase 2 ISOLATE:\n- Network logs: token arrives intact\n- Auth service: token validation fails intermittently\n- Added logging: token format varies slightly\n\nPhase 3 HYPOTHESIZE:\n- Mobile client generates tokens with different encoding\n- v2.3 tightened token validation\n- Theory: mobile token format doesn't match new validation\n\nPhase 4 VERIFY:\n- Fixed token format in mobile client\n- Tested 100 logins on mobile: 100% success\n- Tested desktop: still works\n- Checked logs: no \"Invalid token\" errors\n```\n\n## Trigger Phrases\n\n- \"bug\", \"error\", \"not working\"\n- \"broken\", \"debug\", \"fix this\"\n- \"doesn't work\", \"fails\", \"crash\"\n- \"调试\", \"修复\", \"报错\"\n\n## Integration\n\n- **EVR Framework** — Each phase is Execute/Verify\n- **Cognitive Debt Guard** — Document bugs in code review\n- **Error Recovery** — What to do after finding the cause\n\n## License\n\nMIT\n\nFile v2.0.0:README.md\n\n# Systematic Debugging\n\n> 4-phase root cause process. No guessing, no random fixes.\n\n## 🎯 Problem\n\nDevelopers (and AI agents) waste time on:\n- ❌ Guessing at causes\n- ❌ Making random changes hoping something works\n- ❌ Fixing symptoms instead of root causes\n- ❌ Repeating the same debugging mistakes\n\n## ✅ The 4-Phase Process\n\n### Phase 1: Observe\n- What exactly is happening? Not what you think is happening.\n- Gather facts, not assumptions.\n- Reproduce the issue reliably.\n\n### Phase 2: Hypothesize\n- List all possible causes (brainstorm, don't judge yet)\n- Rank by likelihood\n- Identify what evidence would prove/disprove each\n\n### Phase 3: Verify\n- Test hypotheses in order of likelihood\n- One variable at a time\n- Document results (positive or negative)\n\n### Phase 4: Fix & Prevent\n- Fix the root cause, not the symptom\n- Add a regression test\n- Document the lesson learned\n\n## 📦 Install\n\n```bash\ngit clone https://github.com/aptratcn/systematic-debugging.git\n```\n\n## 🔑 Trigger Words\n\n`debug`, `fix error`, `bug`, `crash`, `not working`, `troubleshoot`\n\n## 📄 License\n\nMIT\n\nFile v2.0.0:_meta.json\n\n{\n  \"ownerId\": \"kn74w4pv5ms0vhet3bstvw95a5833msw\",\n  \"slug\": \"xiaobai-systematic-debugging\",\n  \"version\": \"2.0.0\",\n  \"publishedAt\": 1776762636260\n}\n\nFile v2.0.0:skill-card.md\n\n## Description:\n\nSystematic Debugging guides agents through a four-phase root cause debugging process that gathers evidence, narrows scope, forms a hypothesis, and verifies the fix.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[aptratcn](https://clawhub.ai/user/aptratcn)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and engineers use this skill to guide software debugging work through evidence gathering, scope isolation, hypothesis formation, and verification before declaring a fix complete.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Broad trigger wording may activate the skill for general support requests that mention common debugging terms.\n\nMitigation: Confirm the user wants a structured debugging workflow before applying the full checklist, or narrow activation triggers during packaging.\n\nRisk: Debugging guidance can lead to code or command proposals that are incorrect for the user's environment.\n\nMitigation: Require reproduction details, review proposed changes before execution, and verify with the original failing case and regression checks.\n\n## Reference(s):\n\n\n## Skill Output:\n\n**Output Type(s):** [guidance, markdown, shell commands]\n\n**Output Format:** [Markdown guidance with checklists and inline shell command examples]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [The skill produces procedural debugging guidance and verification prompts rather than executing commands automatically.]\n\n## Skill Version(s):\n\n2.0.0 (source: frontmatter and server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.0: 2 files, 2739 bytes\n\nFiles: SKILL.md (6071b), _meta.json (147b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: systematic-debugging\nversion: 1.0.0\ndescription: Systematic Debugging - 4-phase root cause process. No guessing, no random fixes. Trace evidence, identify root cause, fix systematically.\nemoji: 🔍\ntags: [debugging, troubleshooting, root-cause, systematic, ai-agent]\n---\n\n# Systematic Debugging 🔍\n\n4-phase root cause process. No guessing, no random fixes.\n\n## The Problem\n\nMost AI debugging looks like:\n```\n\"Try X\"\n\"Didn't work\"\n\"Try Y\"\n\"Didn't work\"\n\"Try Z\"\n\"That broke something else\"\n```\n\nThis is not debugging. This is guessing.\n\n## The Solution: 4-Phase Process\n\n### Phase 1: Reproduce & Document 🔒\n\n**Goal:** Establish a reliable reproduction\n\n**Steps:**\n1. Get exact error message\n2. Identify exact conditions that trigger it\n3. Create minimal reproduction case\n4. Document what you know\n\n```\nDocumentation Template:\n\n## Bug Report\n\n**Error Message:**\n[Exact error, full stack trace if available]\n\n**Reproduction Steps:**\n1. [Exact steps to trigger]\n\n**Expected:**\n[What should happen]\n\n**Actual:**\n[What happens instead]\n\n**Environment:**\n- OS: [from uname -a]\n- Version: [from package.json or version command]\n- Last working: [if known]\n- First broken: [if known]\n\n**Minimal Reproduction:**\n[Smallest code that triggers the issue]\n```\n\n**Gate:** Can you reproduce it on command? If no, don't proceed.\n\n### Phase 2: Gather Evidence 🔒\n\n**Goal:** Collect data, not theories\n\n**Steps:**\n1. Check logs (application, system, error)\n2. Add logging/debugging if needed\n3. Compare working vs broken cases\n4. Document findings, not conclusions\n\n```\nEvidence Collection Checklist:\n\n[ ] Application logs checked\n[ ] System logs checked\n[ ] Network requests logged (if applicable)\n[ ] Database queries logged (if applicable)\n[ ] Memory/CPU profile checked (if performance issue)\n[ ] Compared with last known working version\n[ ] Searched for similar issues (GitHub issues, Stack Overflow)\n\nEvidence Table:\n\n| Observation | Data |\n|-------------|------|\n| Error occurs when | [condition] |\n| Error does NOT occur when | [condition] |\n| Related log entries | [entries] |\n| Different in working vs broken | [diffs] |\n```\n\n**Gate:** Do you have concrete evidence, not just theories? If no, gather more.\n\n### Phase 3: Identify Root Cause 🔒\n\n**Goal:** Find THE reason, not A reason\n\n**Steps:**\n1. Form hypothesis based on evidence\n2. Design test to validate hypothesis\n3. Run test\n4. If hypothesis wrong, form new hypothesis (go to step 1)\n5. If right, verify it's THE root cause (not just symptom)\n\n```\nRoot Cause Validation:\n\nHypothesis: [Why you think it happens]\nTest: [How to prove/disprove]\nExpected if hypothesis correct: [What you'll see]\nActual result: [What you actually saw]\n\nRoot Cause vs Symptom Check:\n- Is this the earliest point where things go wrong? → If no, trace back further\n- Would fixing this definitely solve the problem? → If maybe, not root cause yet\n- Can you explain the full chain from this cause to observed error? → If no, gaps exist\n\nRoot Cause Found: [Yes/No]\nIf Yes: [State the root cause]\nIf No: [What else to investigate]\n```\n\n**Gate:** Can you explain the full chain from root cause to observed error? If no, not root cause yet.\n\n### Phase 4: Fix & Verify 🔒\n\n**Goal:** Fix the root cause, verify it works\n\n**Steps:**\n1. Design fix for root cause (not symptom)\n2. Implement fix\n3. Verify original error is gone\n4. Verify fix doesn't break anything else\n5. Add regression test\n6. Document fix\n\n```\nFix Verification Checklist:\n\n[ ] Fix targets root cause, not symptom\n[ ] Original error no longer occurs\n[ ] All existing tests still pass\n[ ] New regression test added\n[ ] Edge cases tested\n[ ] Related functionality verified\n[ ] Fix documented in code comments or docs\n\nBefore/After:\n\n| Metric | Before | After |\n|--------|--------|-------|\n| Error occurs | Yes | No |\n| Tests passing | X/Y | Y/Y |\n| Side effects | N/A | None detected |\n```\n\n**Gate:** All checkboxes checked? If no, not done yet.\n\n## Anti-Patterns\n\n| Anti-Pattern | Why It's Bad | Fix |\n|--------------|--------------|-----|\n| \"Let me try X\" | Random guessing | Reproduce first |\n| \"I think it's...\" | Theory without evidence | Gather evidence |\n| Fixing symptoms | Problem comes back | Find root cause |\n| \"It works now\" | Might not be fixed | Verify systematically |\n| No regression test | Bug comes back | Add test |\n\n## Debugging Decision Tree\n\n```\nError occurs\n    |\n    v\nCan you reproduce it?\n    |\n    +-- No --> Add logging, try again\n    |\n    +-- Yes --> Document reproduction\n                    |\n                    v\n              Evidence gathered?\n                    |\n                    +-- No --> Check logs, add logging, compare versions\n                    |\n                    +-- Yes --> Hypothesis formed?\n                                    |\n                                    +-- No --> Analyze evidence\n                                    |\n                                    +-- Yes --> Test hypothesis\n                                                    |\n                                                    +-- Wrong --> New hypothesis\n                                                    |\n                                                    +-- Right --> Root cause found?\n                                                                    |\n                                                                    +-- No --> Trace back further\n                                                                    |\n                                                                    +-- Yes --> Fix & verify\n```\n\n## Integration with Other Skills\n\n- **EVR Framework** — Fix is executed, verified, reported\n- **Workflow Checkpoint** — Track debugging progress\n- **Error Recovery** — Systematic retry after identifying cause\n\n## Quick Reference\n\n```\nPhase 1: Reproduce → Document exact error and steps\nPhase 2: Evidence → Logs, comparisons, data (no theories yet)\nPhase 3: Root Cause → Hypothesis → Test → Validate\nPhase 4: Fix → Target root cause → Verify → Regression test\n```\n\n## License\n\nMIT\n\nFile v1.0.0:_meta.json\n\n{\n  \"ownerId\": \"kn74w4pv5ms0vhet3bstvw95a5833msw\",\n  \"slug\": \"xiaobai-systematic-debugging\",\n  \"version\": \"1.0.0\",\n  \"publishedAt\": 1776755465825\n}","readmeExcerpt":"Skill: Systematic Debugging Owner: aptratcn Summary: Systematic Debugging - 4-phase root cause process. No guessing, no random fixes. Trace evidence, identify root cause, fix systematically. Tags: debugging:2.0.0, latest:2.0.0, root-cause:1.0.0, systematic:1.0.0, troubleshooting:2.0.0 Version history: v2.0.0 | 2026-04-21T09:10:36.260Z | user v2.0: 4-phase framework with real examples v1.0.0 | 2026-04-21T07:11:05.825Z","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"Phase 1: OBSERVE    → What exactly is wrong? (Gather evidence)\nPhase 2: ISOLATE    → Where does it go wrong? (Narrow scope)\nPhase 3: HYPOTHESIZE → Why does it go wrong? (Form theory)\nPhase 4: VERIFY     → Is it actually fixed? (Prove it)"},{"language":"text","snippet":"□ What is the expected behavior?\n□ What is the actual behavior?\n□ When did it start? (What changed?)\n□ Is it reproducible? (100%? Intermittent?)\n□ What's the exact error message / log output?\n□ What environment? (OS, version, dependencies)"},{"language":"text","snippet":"1. Is the problem in my code or external?\n   → Comment out my code. Still broken? External.\n\n2. Is it in the input, processing, or output?\n   → Print/log at each stage.\n\n3. Is it in one specific file/function?\n   → Remove files/functions one by one.\n   → Bug disappears? That's where it is.\n\n4. Is it a specific condition?\n   → Test with different inputs.\n   → Pattern emerges? Root cause narrows."},{"language":"text","snippet":"I believe [X] is broken because [Y].\n\nEvidence supporting:\n- [Observation 1]\n- [Observation 2]\n\nEvidence against:\n- [Observation 3]\n\nIf I change [Z], the fix should:\n- Make [test case] pass\n- Not break [other thing]"},{"language":"text","snippet":"□ Original test case now passes\n□ Edge cases tested\n□ No new regressions introduced\n□ Error no longer appears in logs\n□ Fix makes sense given the hypothesis"},{"language":"bash","snippet":"# Run the failing test\nnpm test -- --grep \"failing test\"\n# Check logs for errors\ntail -f /var/log/app.log\n# Test edge cases\n[try empty input, huge input, unicode, etc.]\n# Run full test suite\nnpm test"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: systematic-debugging\nversion: 2.0.0\ndescription: 4-phase root cause debugging. Never guess, find the cause. Based on real production debugging methodology. Trigger on: 'bug', 'error', 'not working', 'broken', 'debug', 'fix this'.\nemoji: 🔍\n---\n\n# Systematic Debugging 🔍\n\n4 phases. No guessing. Find root cause.\n\n## The 4 Phases\n\n```\nPhase 1: OBSERVE    → What exactly is wrong? (Gather evidence)\nPhase 2: ISOLATE    → Where does it go wrong? (Narrow scope)\nPhase 3: HYPOTHESIZE → Why does it go wrong? (Form theory)\nPhase 4: VERIFY     → Is it actually fixed? (Prove it)\n```\n\n## Phase 1: OBSERVE (Don't Skip This)\n\n**Before touching any code, answer these:**\n\n```\n□ What is the expected behavior?\n□ What is the actual behavior?\n□ When did it start? (What changed?)\n□ Is it reproducible? (100%? Intermittent?)\n□ What's the exact error message / log output?\n□ What environment? (OS, version, dependencies)\n```\n\n**Common mistake:** Jumping to \"I think it's because...\" without observing first.\n\n**What to do:**\n- Read the actual error (copy-paste, don't paraphrase)\n- Check logs (recent ones first)\n- Reproduce the issue (if possible)\n- Document what you see\n\n## Phase 2: ISOLATE (Narrow the Scope)\n\n**Binary search for the bug:**\n\n```\n1. Is the problem in my code or external?\n   → Comment out my code. Still broken? External.\n\n2. Is it in the input, processing, or output?\n   → Print/log at each stage.\n\n3. Is it in one specific file/function?\n   → Remove files/functions one by one.\n   → Bug disappears? That's where it is.\n\n4. Is it a specific condition?\n   → Test with different inputs.\n   → Pattern emerges? Root cause narrows.\n```\n\n**Techniques:**\n- `git bisect` — Find the commit that introduced the bug\n- Print statements at boundaries\n- Comment out code sections\n- Test with minimal reproduction\n\n## Phase 3: HYPOTHESIZE (Form a Theory)\n\n**Write your hypothesis BEFORE fixing:**\n\n```\nI believe [X] is broken because [Y].\n\nEvidence supporting:\n- [Observation 1]\n- [Observation 2]\n\nEvidence against:\n- [Observation 3]\n\nIf I change [Z], the fix should:\n- Make [test case] pass\n- Not break [other thing]\n```\n\n**Common mistake:** Fixing without understanding. You might \"fix\" the symptom, not the cause.\n\n**Anti-patterns:**\n- ❌ \"Let me try changing this...\" (random fixing)\n- ❌ \"This usually works...\" (cargo cult debugging)\n- ❌ \"It's probably a race condition\" (vague guess)\n\n## Phase 4: VERIFY (Prove It)\n\n**Before claiming \"fixed\":**\n\n```\n□ Original test case now passes\n□ Edge cases tested\n□ No new regressions introduced\n□ Error no longer appears in logs\n□ Fix makes sense given the hypothesis\n```\n\n**Verification checklist:**\n```bash\n# Run the failing test\nnpm test -- --grep \"failing test\"\n# Check logs for errors\ntail -f /var/log/app.log\n# Test edge cases\n[try empty input, huge input, unicode, etc.]\n# Run full test suite\nnpm test\n```\n\n## Real Example\n\n**Bug:** \"User login sometimes fails\"\n\n```\nPhase 1 OBSERVE:\n- Error: \"Invalid token\" (not \"wrong password\")\n- Intermittent (1"},{"path":"README.md","content":"# Systematic Debugging\n\n> 4-phase root cause process. No guessing, no random fixes.\n\n## 🎯 Problem\n\nDevelopers (and AI agents) waste time on:\n- ❌ Guessing at causes\n- ❌ Making random changes hoping something works\n- ❌ Fixing symptoms instead of root causes\n- ❌ Repeating the same debugging mistakes\n\n## ✅ The 4-Phase Process\n\n### Phase 1: Observe\n- What exactly is happening? Not what you think is happening.\n- Gather facts, not assumptions.\n- Reproduce the issue reliably.\n\n### Phase 2: Hypothesize\n- List all possible causes (brainstorm, don't judge yet)\n- Rank by likelihood\n- Identify what evidence would prove/disprove each\n\n### Phase 3: Verify\n- Test hypotheses in order of likelihood\n- One variable at a time\n- Document results (positive or negative)\n\n### Phase 4: Fix & Prevent\n- Fix the root cause, not the symptom\n- Add a regression test\n- Document the lesson learned\n\n## 📦 Install\n\n```bash\ngit clone https://github.com/aptratcn/systematic-debugging.git\n```\n\n## 🔑 Trigger Words\n\n`debug`, `fix error`, `bug`, `crash`, `not working`, `troubleshoot`\n\n## 📄 License\n\nMIT"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn74w4pv5ms0vhet3bstvw95a5833msw\",\n  \"slug\": \"xiaobai-systematic-debugging\",\n  \"version\": \"2.0.0\",\n  \"publishedAt\": 1776762636260\n}"},{"path":"skill-card.md","content":"## Description:\n\nSystematic Debugging guides agents through a four-phase root cause debugging process that gathers evidence, narrows scope, forms a hypothesis, and verifies the fix.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[aptratcn](https://clawhub.ai/user/aptratcn)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and engineers use this skill to guide software debugging work through evidence gathering, scope isolation, hypothesis formation, and verification before declaring a fix complete.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Broad trigger wording may activate the skill for general support requests that mention common debugging terms.\n\nMitigation: Confirm the user wants a structured debugging workflow before applying the full checklist, or narrow activation triggers during packaging.\n\nRisk: Debugging guidance can lead to code or command proposals that are incorrect for the user's environment.\n\nMitigation: Require reproduction details, review proposed changes before execution, and verify with the original failing case and regression checks.\n\n## Reference(s):\n\n\n## Skill Output:\n\n**Output Type(s):** [guidance, markdown, shell commands]\n\n**Output Format:** [Markdown guidance with checklists and inline shell command examples]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [The skill produces procedural debugging guidance and verification prompts rather than executing commands automatically.]\n\n## Skill Version(s):\n\n2.0.0 (source: frontmatter and server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Systematic Debugging - 4-phase root cause process. No guessing, no random fixes. Trace evidence, identify root cause, fix systematically. Skill: Systematic Debugging Owner: aptratcn Summary: Systematic Debugging - 4-phase root cause process. No guessing, no random fixes. Trace evidence, identify root cause, fix systematically. Tags: debugging:2.0.0, latest:2.0.0, root-cause:1.0.0, systematic:1.0.0, troubleshooting:2.0.0 Version history: v2.0.0 | 2026-04-21T09:10:36.260Z | user v2.0: 4-phase framework with real examples v1.0.0 | 2026-04-21T07:11:05.825Z","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":828,"uniquenessScore":61,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T22:40:23.143Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T22:40:23.143Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-12T18:16:04.977Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}