[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75E2V33NJSQDYKZTND4NAPJ":3,"skill-same:01M75E2V33NJSQDYKZTND4NAPJ":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75E2V33NJSQDYKZTND4NAPJ","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.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fgstack-openclaw-investigate\u002FSKILL.md",[],[],"2026-11-12 13:55:43",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","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fgstack-openclaw-investigate",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill gstack-openclaw-investigate",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill gstack-openclaw-investigate",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill gstack-openclaw-investigate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fgstack-openclaw-investigate\u002FSKILL.md",true,[],[47,54,61,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]