[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MG86TGGP1B1SWDZX5VWS76":3,"skill-same:01M6MG86TGGP1B1SWDZX5VWS76":66},{"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":23,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":47,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M6MG86TGGP1B1SWDZX5VWS76","debug",null,"Systematic root-cause isolation for test failures, runtime errors, or unexpected behavior. Narrow hypothesis → verify → fix.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fepicsagas\u002Fepic-harness\u002Fskills\u002Fdebug\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[5,24,25,26,27,28,29,30,31,32,33,34,35,36],"test","observability","hypothesis","verify","behavior","fix","root-cause","runtime","systematic","isolation","errors","root","for","2026-11-10 10:12:30",false,"---\nname: debug\ndimension: observability\ndescription: \"Systematic root-cause isolation for test failures, runtime errors, or unexpected behavior. Narrow hypothesis → verify → fix.\"\n---\n\n# Debug — Systematic Debugging\n\n## Iron Law\n\nNO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST. Symptom fixes are whack-a-mole debugging.\n\n## Process\n\n### 0. Recall\n- Query the knowledge graph: `epic mem search \"ERROR_MESSAGE_OR_FILE\"` for the error message or file name\n- Check if a `resolution` or `pattern` node exists for this error category\n- If a past resolution exists, apply it directly instead of re-debugging from scratch\n\n**Why**: Past resolutions save 10-30 minutes of re-investigation. The knowledge graph exists so you don't repeat work.\n\n### 1. Observe\n- Read the full error message and stack trace\n- Identify: What was expected? What actually happened?\n- Note the exact file, line, and function\n\n**Why**: Precise observation prevents misdiagnosis. Most debug loops start from skimming the error instead of reading it fully.\n\n### 2. Hypothesize\nForm 2-3 possible causes. Rank by likelihood.\n\n**Why**: Ranked hypotheses prevent random code changes. Even a wrong hypothesis narrows the search space.\n\n### 3. Isolate\n- **Narrow the scope**: Binary search through recent changes\n- **Reproduce minimally**: Smallest input that triggers the error\n- **Check assumptions**: Print\u002Flog intermediate values\n- **Bisect**: `git log --oneline -10` — when did it last work?\n\n**Why**: Isolation proves the cause before you touch any code. Without it, you're guessing.\n\n### 4. Fix\n- Fix the root cause, not the symptom\n- If the fix is a workaround, add a TODO with explanation\n\n**Why**: Root cause fixes are permanent. Symptom patches rot and hide the real bug.\n\n### 5. Verify\n- Run the failing test — must pass now\n- Run the full test suite — no regressions\n- If this was a bug, the regression test stays\n\n**Why**: A passing fix without verification is wishful thinking. The full suite catches side effects.\n\n### 6. Record\n- If the fix involved 3+ debug steps, record a `resolution` node via `epic mem add --title \"...\" --type resolution --body \"...\"`\n- Include: error category, root cause, solution approach\n- This enables future sessions to skip re-debugging the same class of issues\n\n**Why**: Recording turns one-time debugging into institutional knowledge. Future sessions benefit from your effort.\n\n## When to Trigger\n- Any test failure during `\u002Fgo` execution\n- Runtime error in tool output\n- \"Unexpected\" in any output\n\n## Anti-Rationalization\n\n| Excuse | Rebuttal | What to do instead |\n|--------|----------|-------------------|\n| \"Let me just try again\" | Retrying without changing anything is not debugging. | Form a new hypothesis before each attempt. |\n| \"It works on my machine\" | Environment differences are bugs too. | Reproduce in the actual target environment first. |\n| \"I'll just catch the exception\" | That hides the bug, doesn't fix it. | Fix the root cause. Only catch what you can handle meaningfully. |\n| \"It's probably a flaky test\" | Flaky tests hide real bugs. Prove it's flaky before dismissing. | Run it 3x in isolation. If it fails consistently, it's real. |\n| \"I'll add more logging\" | Logging without a hypothesis is fishing. | Hypothesize first, then add targeted logging to confirm\u002Fdeny. |\n| \"It's probably just a typo\" | Assumptions are the enemy of debugging. Reproduce first, then diagnose. | Read the full error, reproduce it, and verify before assuming simplicity. |\n| \"Let me just try changing this one thing\" | Whack-a-mole debugging creates more bugs. Follow the hypothesis → isolate → fix cycle. | Form a hypothesis, isolate the cause, then fix with evidence. |\n| \"The error message tells me everything\" | Error messages describe symptoms, not root causes. Investigate the chain. | Trace the error to its origin. The message is the starting point, not the answer. |\n\n## Evidence Required\n\nBefore claiming the bug is fixed, show ALL of these:\n\n- [ ] Root cause identified: one sentence explaining WHY it broke\n- [ ] Fix applied: diff showing the change\n- [ ] Previously failing test now passes (show output)\n- [ ] Full test suite passes (no regressions)\n- [ ] If bug came from a pattern, regression test added to prevent recurrence\n\n**\"It works now\" without root cause = symptom patch, not a fix.**\n\n## Red Flags\n- Changing random things hoping something works\n- More than 3 retry attempts without forming a new hypothesis\n- Suppressing errors instead of fixing them\n","# Debug — Systematic Debugging\n\n## Iron Law\n\nNO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST. Symptom fixes are whack-a-mole debugging.\n\n## Process\n\n### 0. Recall\n- Query the knowledge graph: `epic mem search \"ERROR_MESSAGE_OR_FILE\"` for the error message or file name\n- Check if a `resolution` or `pattern` node exists for this error category\n- If a past resolution exists, apply it directly instead of re-debugging from scratch\n\n**Why**: Past resolutions save 10-30 minutes of re-investigation. The knowledge graph exists so you don't repeat work.\n\n### 1. Observe\n- Read the full error message and stack trace\n- Identify: What was expected? What actually happened?\n- Note the exact file, line, and function\n\n**Why**: Precise observation prevents misdiagnosis. Most debug loops start from skimming the error instead of reading it fully.\n\n### 2. Hypothesize\nForm 2-3 possible causes. Rank by likelihood.\n\n**Why**: Ranked hypotheses prevent random code changes. Even a wrong hypothesis narrows the search space.\n\n### 3. Isolate\n- **Narrow the scope**: Binary search through recent changes\n- **Reproduce minimally**: Smallest input that triggers the error\n- **Check assumptions**: Print\u002Flog intermediate values\n- **Bisect**: `git log --oneline -10` — when did it last work?\n\n**Why**: Isolation proves the cause before you touch any code. Without it, you're guessing.\n\n### 4. Fix\n- Fix the root cause, not the symptom\n- If the fix is a workaround, add a TODO with explanation\n\n**Why**: Root cause fixes are permanent. Symptom patches rot and hide the real bug.\n\n### 5. Verify\n- Run the failing test — must pass now\n- Run the full test suite — no regressions\n- If this was a bug, the regression test stays\n\n**Why**: A passing fix without verification is wishful thinking. The full suite catches side effects.\n\n### 6. Record\n- If the fix involved 3+ debug steps, record a `resolution` node via `epic mem add --title \"...\" --type resolution --body \"...\"`\n- Include: error category, root cause, solution approach\n- This enables future sessions to skip re-debugging the same class of issues\n\n**Why**: Recording turns one-time debugging into institutional knowledge. Future sessions benefit from your effort.\n\n## When to Trigger\n- Any test failure during `\u002Fgo` execution\n- Runtime error in tool output\n- \"Unexpected\" in any output\n\n## Anti-Rationalization\n\n| Excuse | Rebuttal | What to do instead |\n|--------|----------|-------------------|\n| \"Let me just try again\" | Retrying without changing anything is not debugging. | Form a new hypothesis before each attempt. |\n| \"It works on my machine\" | Environment differences are bugs too. | Reproduce in the actual target environment first. |\n| \"I'll just catch the exception\" | That hides the bug, doesn't fix it. | Fix the root cause. Only catch what you can handle meaningfully. |\n| \"It's probably a flaky test\" | Flaky tests hide real bugs. Prove it's flaky before dismissing. | Run it 3x in isolation. If it fails consistently, it's real. |\n| \"I'll add more logging\" | Logging without a hypothesis is fishing. | Hypothesize first, then add targeted logging to confirm\u002Fdeny. |\n| \"It's probably just a typo\" | Assumptions are the enemy of debugging. Reproduce first, then diagnose. | Read the full error, reproduce it, and verify before assuming simplicity. |\n| \"Let me just try changing this one thing\" | Whack-a-mole debugging creates more bugs. Follow the hypothesis → isolate → fix cycle. | Form a hypothesis, isolate the cause, then fix with evidence. |\n| \"The error message tells me everything\" | Error messages describe symptoms, not root causes. Investigate the chain. | Trace the error to its origin. The message is the starting point, not the answer. |\n\n## Evidence Required\n\nBefore claiming the bug is fixed, show ALL of these:\n\n- [ ] Root cause identified: one sentence explaining WHY it broke\n- [ ] Fix applied: diff showing the change\n- [ ] Previously failing test now passes (show output)\n- [ ] Full test suite passes (no regressions)\n- [ ] If bug came from a pattern, regression test added to prevent recurrence\n\n**\"It works now\" without root cause = symptom patch, not a fix.**\n\n## Red Flags\n- Changing random things hoping something works\n- More than 3 retry attempts without forming a new hypothesis\n- Suppressing errors instead of fixing them\n",{"name":5,"dimension":25,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fepicsagas\u002Fepic-harness\u002Fskills\u002Fdebug",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill debug",{"tool":58,"command":59},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill debug",{"tool":61,"command":62},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill debug","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fepicsagas\u002Fepic-harness\u002Fskills\u002Fdebug\u002FSKILL.md",true,[],[67,77,85,93,101,109],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":72,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":76},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":76},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":76},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":76},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":76},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":76},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]