[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78ZVRVMQCNF853RXYCEB07A":3,"skill-same:01M78ZVRVMQCNF853RXYCEB07A":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M78ZVRVMQCNF853RXYCEB07A","gstack-openclaw-investigate",null,"Use when asked to debug, fix a bug, investigate an error, or do root cause analysis, and when users report errors, stack traces, unexpected behavior, or say something stopped working.","justeozan\u002Fvox","justeozan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F117074595?v=4","01M78ZMF2Q9GPWSZTY7DEYHZ03","Ozan S.","01M78ZMF3APNA8M79PDPMT26QF",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjusteozan\u002Fvox\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgstack\u002Fopenclaw\u002Fskills\u002Fgstack-openclaw-investigate\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: gstack-openclaw-investigate\ndescription: Use when asked to debug, fix a bug, investigate an error, or do root cause analysis, and when users report errors, stack traces, unexpected behavior, or say something stopped working.\n---\n\n# Systematic Debugging\n\n## Iron Law\n\n**NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST.**\n\nFixing symptoms creates whack-a-mole debugging. Every fix that doesn't address root cause makes the next bug harder to find. Find the root cause, then fix it.\n\n---\n\n## Phase 1: Root Cause Investigation\n\nGather context before forming any hypothesis.\n\n1. **Collect symptoms:** Read the error messages, stack traces, and reproduction steps. If the user hasn't provided enough context, ask ONE question at a time. Don't ask five questions at once.\n\n2. **Read the code:** Trace the code path from the symptom back to potential causes. Search for all references, read the logic around the failure point.\n\n3. **Check recent changes:**\n   ```bash\n   git log --oneline -20 -- \u003Caffected-files>\n   ```\n   Was this working before? What changed? A regression means the root cause is in the diff.\n\n4. **Reproduce:** Can you trigger the bug deterministically? If not, gather more evidence before proceeding.\n\n5. **Check memory** for prior debugging sessions on the same area. Recurring bugs in the same files are an architectural smell.\n\nOutput: **\"Root cause hypothesis: ...\"** ... a specific, testable claim about what is wrong and why.\n\n---\n\n## Phase 2: Pattern Analysis\n\nCheck if this bug matches a known pattern:\n\n**Race condition** ... Intermittent, timing-dependent. Look at concurrent access to shared state.\n\n**Nil\u002Fnull propagation** ... NoMethodError, TypeError. Missing guards on optional values.\n\n**State corruption** ... Inconsistent data, partial updates. Check transactions, callbacks, hooks.\n\n**Integration failure** ... Timeout, unexpected response. External API calls, service boundaries.\n\n**Configuration drift** ... Works locally, fails in staging\u002Fprod. Env vars, feature flags, DB state.\n\n**Stale cache** ... Shows old data, fixes on cache clear. Redis, CDN, browser cache.\n\nAlso check:\n- Known issues in the project for related problems\n- Git log for prior fixes in the same area. Recurring bugs in the same files are an architectural smell, not a coincidence.\n\n**External search:** If the bug doesn't match a known pattern, search for the error type online. **Sanitize first:** strip hostnames, IPs, file paths, SQL, customer data. Search the error category, not the raw message.\n\n---\n\n## Phase 3: Hypothesis Testing\n\nBefore writing ANY fix, verify your hypothesis.\n\n1. **Confirm the hypothesis:** Add a temporary log statement, assertion, or debug output at the suspected root cause. Run the reproduction. Does the evidence match?\n\n2. **If the hypothesis is wrong:** Search for the error (sanitize sensitive data first). Return to Phase 1. Gather more evidence. Do not guess.\n\n3. **3-strike rule:** If 3 hypotheses fail, **STOP**. Tell the user:\n\n   \"3 hypotheses tested, none match. This may be an architectural issue rather than a simple bug.\"\n\n   Options:\n   - Continue investigating with a new hypothesis (describe it)\n   - Escalate for human review (needs someone who knows the system)\n   - Add logging and wait (instrument the area and catch it next time)\n\n**Red flags** ... if you see any of these, slow down:\n- \"Quick fix for now\" ... there is no \"for now.\" Fix it right or escalate.\n- Proposing a fix before tracing data flow ... you're guessing.\n- Each fix reveals a new problem elsewhere ... wrong layer, not wrong code.\n\n---\n\n## Phase 4: Implementation\n\nOnce root cause is confirmed:\n\n1. **Fix the root cause, not the symptom.** The smallest change that eliminates the actual problem.\n\n2. **Minimal diff:** Fewest files touched, fewest lines changed. Resist the urge to refactor adjacent code.\n\n3. **Write a regression test** that:\n   - **Fails** without the fix (proves the test is meaningful)\n   - **Passes** with the fix (proves the fix works)\n\n4. **Run the full test suite.** No regressions allowed.\n\n5. **If the fix touches >5 files:** Flag the blast radius to the user before proceeding. That's large for a bug fix.\n\n---\n\n## Phase 5: Verification & Report\n\n**Fresh verification:** Reproduce the original bug scenario and confirm it's fixed. This is not optional.\n\nRun the test suite.\n\nOutput a structured debug report:\n\n**DEBUG REPORT**\n- **Symptom:** what the user observed\n- **Root cause:** what was actually wrong\n- **Fix:** what was changed, with file references\n- **Evidence:** test output, reproduction showing fix works\n- **Regression test:** location of the new test\n- **Related:** prior bugs in same area, architectural notes\n- **Status:** DONE | DONE_WITH_CONCERNS | BLOCKED\n\nSave the report to `memory\u002F` with today's date so future sessions can reference it.\n\n---\n\n## Important Rules\n\n- **3+ failed fix attempts: STOP and question the architecture.** Wrong architecture, not failed hypothesis.\n- **Never apply a fix you cannot verify.** If you can't reproduce and confirm, don't ship it.\n- **Never say \"this should fix it.\"** Verify and prove it. Run the tests.\n- **If fix touches >5 files:** Flag to user before proceeding.\n- **Completion status:**\n  - DONE ... root cause found, fix applied, regression test written, all tests pass\n  - DONE_WITH_CONCERNS ... fixed but cannot fully verify (e.g., intermittent bug, requires staging)\n  - BLOCKED ... root cause unclear after investigation, escalated\n","# Systematic Debugging\n\n## Iron Law\n\n**NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST.**\n\nFixing symptoms creates whack-a-mole debugging. Every fix that doesn't address root cause makes the next bug harder to find. Find the root cause, then fix it.\n\n---\n\n## Phase 1: Root Cause Investigation\n\nGather context before forming any hypothesis.\n\n1. **Collect symptoms:** Read the error messages, stack traces, and reproduction steps. If the user hasn't provided enough context, ask ONE question at a time. Don't ask five questions at once.\n\n2. **Read the code:** Trace the code path from the symptom back to potential causes. Search for all references, read the logic around the failure point.\n\n3. **Check recent changes:**\n   ```bash\n   git log --oneline -20 -- \u003Caffected-files>\n   ```\n   Was this working before? What changed? A regression means the root cause is in the diff.\n\n4. **Reproduce:** Can you trigger the bug deterministically? If not, gather more evidence before proceeding.\n\n5. **Check memory** for prior debugging sessions on the same area. Recurring bugs in the same files are an architectural smell.\n\nOutput: **\"Root cause hypothesis: ...\"** ... a specific, testable claim about what is wrong and why.\n\n---\n\n## Phase 2: Pattern Analysis\n\nCheck if this bug matches a known pattern:\n\n**Race condition** ... Intermittent, timing-dependent. Look at concurrent access to shared state.\n\n**Nil\u002Fnull propagation** ... NoMethodError, TypeError. Missing guards on optional values.\n\n**State corruption** ... Inconsistent data, partial updates. Check transactions, callbacks, hooks.\n\n**Integration failure** ... Timeout, unexpected response. External API calls, service boundaries.\n\n**Configuration drift** ... Works locally, fails in staging\u002Fprod. Env vars, feature flags, DB state.\n\n**Stale cache** ... Shows old data, fixes on cache clear. Redis, CDN, browser cache.\n\nAlso check:\n- Known issues in the project for related problems\n- Git log for prior fixes in the same area. Recurring bugs in the same files are an architectural smell, not a coincidence.\n\n**External search:** If the bug doesn't match a known pattern, search for the error type online. **Sanitize first:** strip hostnames, IPs, file paths, SQL, customer data. Search the error category, not the raw message.\n\n---\n\n## Phase 3: Hypothesis Testing\n\nBefore writing ANY fix, verify your hypothesis.\n\n1. **Confirm the hypothesis:** Add a temporary log statement, assertion, or debug output at the suspected root cause. Run the reproduction. Does the evidence match?\n\n2. **If the hypothesis is wrong:** Search for the error (sanitize sensitive data first). Return to Phase 1. Gather more evidence. Do not guess.\n\n3. **3-strike rule:** If 3 hypotheses fail, **STOP**. Tell the user:\n\n   \"3 hypotheses tested, none match. This may be an architectural issue rather than a simple bug.\"\n\n   Options:\n   - Continue investigating with a new hypothesis (describe it)\n   - Escalate for human review (needs someone who knows the system)\n   - Add logging and wait (instrument the area and catch it next time)\n\n**Red flags** ... if you see any of these, slow down:\n- \"Quick fix for now\" ... there is no \"for now.\" Fix it right or escalate.\n- Proposing a fix before tracing data flow ... you're guessing.\n- Each fix reveals a new problem elsewhere ... wrong layer, not wrong code.\n\n---\n\n## Phase 4: Implementation\n\nOnce root cause is confirmed:\n\n1. **Fix the root cause, not the symptom.** The smallest change that eliminates the actual problem.\n\n2. **Minimal diff:** Fewest files touched, fewest lines changed. Resist the urge to refactor adjacent code.\n\n3. **Write a regression test** that:\n   - **Fails** without the fix (proves the test is meaningful)\n   - **Passes** with the fix (proves the fix works)\n\n4. **Run the full test suite.** No regressions allowed.\n\n5. **If the fix touches >5 files:** Flag the blast radius to the user before proceeding. That's large for a bug fix.\n\n---\n\n## Phase 5: Verification & Report\n\n**Fresh verification:** Reproduce the original bug scenario and confirm it's fixed. This is not optional.\n\nRun the test suite.\n\nOutput a structured debug report:\n\n**DEBUG REPORT**\n- **Symptom:** what the user observed\n- **Root cause:** what was actually wrong\n- **Fix:** what was changed, with file references\n- **Evidence:** test output, reproduction showing fix works\n- **Regression test:** location of the new test\n- **Related:** prior bugs in same area, architectural notes\n- **Status:** DONE | DONE_WITH_CONCERNS | BLOCKED\n\nSave the report to `memory\u002F` with today's date so future sessions can reference it.\n\n---\n\n## Important Rules\n\n- **3+ failed fix attempts: STOP and question the architecture.** Wrong architecture, not failed hypothesis.\n- **Never apply a fix you cannot verify.** If you can't reproduce and confirm, don't ship it.\n- **Never say \"this should fix it.\"** Verify and prove it. Run the tests.\n- **If fix touches >5 files:** Flag to user before proceeding.\n- **Completion status:**\n  - DONE ... root cause found, fix applied, regression test written, all tests pass\n  - DONE_WITH_CONCERNS ... fixed but cannot fully verify (e.g., intermittent bug, requires staging)\n  - BLOCKED ... root cause unclear after investigation, escalated\n",{"name":5,"description":7},"main","dba8e23bc1f3b80d9a984cfba6f07ea7cf6eeef2",".claude\u002Fskills\u002Fgstack\u002Fopenclaw\u002Fskills\u002Fgstack-openclaw-investigate","https:\u002F\u002Fgithub.com\u002Fjusteozan\u002Fvox","https:\u002F\u002Fjusteozan.github.io\u002Fvox\u002F","https:\u002F\u002Fgithub.com\u002Fjusteozan","https:\u002F\u002Fjusteozan.evey.run","👋 Welcome to my GitHub! I'm a cybersecurity enthusiast. Explore my projects and share your feedback. 📡","2026-11-07 02:21:49",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add justeozan\u002Fvox --skill gstack-openclaw-investigate",{"tool":39,"command":40},"bunx","bunx skills add justeozan\u002Fvox --skill gstack-openclaw-investigate",{"tool":42,"command":43},"pnpm","pnpm dlx skills add justeozan\u002Fvox --skill gstack-openclaw-investigate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjusteozan\u002Fvox\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgstack\u002Fopenclaw\u002Fskills\u002Fgstack-openclaw-investigate\u002FSKILL.md",true,[],[48,54,60,66,72,78],{"skillNo":49,"name":50,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7901B5DR5HWEDJ5MJ3NYSNA","unfreeze","https:\u002F\u002Fgithub.com\u002Fjusteozan\u002Fvox\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Funfreeze\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7901A8WH5F7HV75YE0XDM88","sync-gbrain","https:\u002F\u002Fgithub.com\u002Fjusteozan\u002Fvox\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsync-gbrain\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M790187P6HDEZWG03M3MNAA2","spec","https:\u002F\u002Fgithub.com\u002Fjusteozan\u002Fvox\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fspec\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M79017C0CC6SAMK1PQM94EVY","skillify","https:\u002F\u002Fgithub.com\u002Fjusteozan\u002Fvox\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fskillify\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M79016E4RDHZB74FBYBT41XX","ship","https:\u002F\u002Fgithub.com\u002Fjusteozan\u002Fvox\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fship\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M79014C0R022XD2TC4Q20NG1","setup-gbrain","https:\u002F\u002Fgithub.com\u002Fjusteozan\u002Fvox\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsetup-gbrain\u002FSKILL.md",[],[]]