[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AS5ZCJX21NF2RESA2QDWPP":3,"skill-same:01M7AS5ZCJX21NF2RESA2QDWPP":74},{"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":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7AS5ZCJX21NF2RESA2QDWPP","systematic-debugging",null,"Root-cause debugging for concrete technical failures including bugs, failing builds or tests, integration issues, performance regressions, and unexpected behavior. Use before proposing or implementing a repair when diagnosis is required. Reproduce the symptom, trace the responsible owner, maintain one leading causal hypothesis, and falsify it with the smallest direct evidence. Compose with Causal Coding for source mutation; testing is opt-in and requires independent authorization.","ham-zax\u002Fwebharness","ham-zax","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F81289670?v=4","01M7AQGHAV4TPYCAZY23S7SVSC","Ahmed Hamza","01M7AQGHBCFJYE7KWZ34W9HEGH",0,"MIT","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: systematic-debugging\ndescription: Root-cause debugging for concrete technical failures including bugs, failing builds or tests, integration issues, performance regressions, and unexpected behavior. Use before proposing or implementing a repair when diagnosis is required. Reproduce the symptom, trace the responsible owner, maintain one leading causal hypothesis, and falsify it with the smallest direct evidence. Compose with Causal Coding for source mutation; testing is opt-in and requires independent authorization.\n---\n\n# Systematic Debugging\n\n## Overview\n\n**Core principle:** Find the root cause before attempting a repair. Do not patch the visible symptom while the responsible owner remains unknown.\n\nCausal Coding remains authoritative for mutation scope, testing authorization, verification cadence, and stopping. This Skill governs diagnosis: establish the visible failure, demonstrated mismatch, violated invariant, responsible owner, and a falsifiable repair hypothesis.\n\nTesting is opt-in. Debugging requires a reproducible symptom and falsifiable evidence, not automatically an automated test. Create, modify, or run tests only when the user, authoritative user-approved specification, or mandatory repository policy explicitly authorizes testing.\n\n## The Iron Law\n\n```\nNO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST\n```\n\nIf you haven't completed Phase 1, you cannot propose fixes.\n\n## The Four Phases\n\nYou MUST complete each phase before proceeding to the next.\n\n### Phase 1: Root Cause Investigation\n\n**BEFORE attempting ANY fix:**\n\n1. **Read Error Messages Carefully**\n   - Don't skip past errors or warnings\n   - They often contain the exact solution\n   - Read stack traces completely\n   - Note line numbers, file paths, error codes\n\n2. **Reproduce Consistently**\n   - Can you trigger it reliably?\n   - What are the exact steps?\n   - Does it happen every time?\n   - If not reproducible → gather more data, don't guess\n\n3. **Check Recent Changes**\n   - What changed that could cause this?\n   - Git diff, recent commits\n   - New dependencies, config changes\n   - Environmental differences\n\n4. **Gather Evidence in Multi-Component Systems**\n\n   **WHEN system has multiple components (CI → build → signing, API → service → database):**\n\n   **BEFORE proposing fixes, add diagnostic instrumentation:**\n   ```\n   For EACH component boundary:\n     - Log what data enters component\n     - Log what data exits component\n     - Verify environment\u002Fconfig propagation\n     - Check state at each layer\n\n   Run once to gather evidence showing WHERE it breaks\n   THEN analyze evidence to identify failing component\n   THEN investigate that specific component\n   ```\n\n   **Example (multi-layer system):**\n   ```bash\n   # Layer 1: Workflow\n   echo \"=== Secrets available in workflow: ===\"\n   echo \"IDENTITY: ${IDENTITY:+SET}${IDENTITY:-UNSET}\"\n\n   # Layer 2: Build script\n   echo \"=== Env vars in build script: ===\"\n   env | grep IDENTITY || echo \"IDENTITY not in environment\"\n\n   # Layer 3: Signing script\n   echo \"=== Keychain state: ===\"\n   security list-keychains\n   security find-identity -v\n\n   # Layer 4: Actual signing\n   codesign --sign \"$IDENTITY\" --verbose=4 \"$APP\"\n   ```\n\n   **This reveals:** Which layer fails (secrets → workflow ✓, workflow → build ✗)\n\n5. **Trace Data Flow**\n\n   **WHEN error is deep in call stack:**\n\n   Read [references\u002Froot-cause-tracing.md](references\u002Froot-cause-tracing.md) when the failure is deep in a call chain or the bad value's origin is unclear.\n\n   **Quick version:**\n   - Where does bad value originate?\n   - What called this with bad value?\n   - Keep tracing up until you find the source\n   - Fix at source, not at symptom\n\n### Phase 2: Pattern Analysis\n\n**Find the pattern before fixing:**\n\n1. **Find Working Examples**\n   - Locate similar working code in same codebase\n   - What works that's similar to what's broken?\n\n2. **Compare Against References**\n   - If an existing implementation or documented pattern governs the broken path, read the smallest relevant material that establishes its contract\n   - Expand only when a concrete unanswered question could change the diagnosis\n   - Understand the required pattern before applying it\n\n3. **Identify Differences**\n   - What's different between working and broken?\n   - List every difference, however small\n   - Don't assume \"that can't matter\"\n\n4. **Understand Dependencies**\n   - What other components does this need?\n   - What settings, config, environment?\n   - What assumptions does it make?\n\n### Phase 3: Hypothesis and Falsification\n\n**Scientific method:**\n\n1. **Form One Leading Hypothesis**\n   - State clearly: \"I think X is the root cause because Y\"\n   - Be specific and falsifiable\n   - Keep one leading hypothesis at a time\n\n2. **Falsify Minimally**\n   - Use the smallest observation, command, runtime probe, or reversible change that can disprove the hypothesis\n   - One variable at a time\n   - Do not stack candidate fixes\n   - An automated test is only one possible probe and still requires independent testing authorization\n\n3. **Evaluate Before Continuing**\n   - Supported? Proceed to Phase 4\n   - Contradicted? Return to the smallest reproduction and form a new hypothesis\n   - Do not add more fixes on top\n\n4. **When You Don't Know**\n   - Say \"I don't understand X\"\n   - Don't pretend to know\n   - Ask for help\n   - Research more\n\n### Phase 4: Implementation\n\n**Fix the root cause, not the symptom:**\n\n1. **Establish a Failing Reproduction**\n   - Use the simplest observable reproduction of the real symptom\n   - Prefer direct runtime\u002Finput\u002Foutput evidence when that is sufficient\n   - Use an automated test only when testing is explicitly authorized\n   - Do not create a one-off test script merely to manufacture a test requirement\n   - The reproduction must be capable of disproving the proposed fix\n\n2. **Implement Single Fix**\n   - Address the root cause identified\n   - ONE change at a time\n   - No \"while I'm here\" improvements\n   - No bundled refactoring\n\n3. **Verify Fix**\n   - Does the original reproduction now succeed?\n   - Is the violated invariant restored at the responsible boundary?\n   - Run tests only when testing is independently authorized; otherwise do not expand the validation surface just because a bug was fixed\n   - Use the completion-evidence workflow before claiming success\n\n4. **If the Repair Doesn't Work**\n   - STOP and return to the original reproduction\n   - If two repair attempts were based on the same causal hypothesis, do not make a third repair under that hypothesis\n   - Re-establish the mismatch and responsible owner from new evidence before another repair\n   - Do not stack patches merely because the previous one failed\n\n5. **Question Architecture Only When Evidence Requires It**\n\n   **Signals of an architectural problem:**\n   - distinct evidence-backed repairs repeatedly expose the same shared-state or coupling flaw across owners\n   - the responsible invariant cannot be restored without changing an actual architecture or public-contract boundary\n   - each local repair necessarily creates a new failure elsewhere\n\n   If the evidence now requires an architectural or public-contract decision, stop and surface that boundary before redesigning. Repeated failed guesses alone do not justify a rewrite.\n\n## Red Flags - STOP and Follow Process\n\nIf you catch yourself thinking:\n- \"Quick fix for now, investigate later\"\n- \"Just try changing X and see if it works\"\n- \"Add multiple changes and see what happens\"\n- \"Skip the reproduction; I'll just eyeball the fix\"\n- \"It's probably X, let me fix that\"\n- \"I don't fully understand but this might work\"\n- \"Pattern says X but I'll adapt it differently\"\n- \"Here are the main problems: [lists fixes without investigation]\"\n- Proposing solutions before tracing data flow\n- **\"One more fix attempt\" under a causal hypothesis that already failed twice**\n- **Each attempted repair reveals a different owner without new evidence**\n\n**ALL of these mean: STOP. Return to Phase 1.**\n\nQuestion architecture only when evidence establishes an architectural boundary, not merely because several guesses failed.\n\n## your human partner's Signals You're Doing It Wrong\n\n**Watch for these redirections:**\n- \"Is that not happening?\" - You assumed without verifying\n- \"Will it show us...?\" - You should have added evidence gathering\n- \"Stop guessing\" - You're proposing fixes without understanding\n- \"Ultra-think this\" - Question fundamentals, not just symptoms\n- \"We're stuck?\" (frustrated) - Your approach isn't working\n\n**When you see these:** STOP. Return to Phase 1.\n\n## Common Rationalizations\n\n| Excuse | Reality |\n|--------|---------|\n| \"Issue is simple, don't need process\" | Simple issues have root causes too. Process is fast for simple bugs. |\n| \"Emergency, no time for process\" | Systematic debugging is FASTER than guess-and-check thrashing. |\n| \"Just try this first, then investigate\" | First fix sets the pattern. Do it right from the start. |\n| \"I'll add a test because this is a bug fix\" | A bug fix requires a falsifiable reproduction; automated testing is separate and only in scope when independently authorized. |\n| \"Multiple fixes at once saves time\" | You cannot isolate what changed the outcome. Make one causal repair at a time. |\n| \"Reference too long, I'll adapt the pattern\" | Read the relevant contract and governing implementation closely enough to know which differences matter; do not substitute guesswork for evidence. |\n| \"I see the problem, let me fix it\" | Seeing symptoms ≠ understanding root cause. |\n| \"One more fix attempt\" under the same twice-failed hypothesis | Return to the original reproduction and establish a new evidence-backed hypothesis before another repair. |\n\n## Quick Reference\n\n| Phase | Key Activities | Success Criteria |\n|-------|---------------|------------------|\n| **1. Root Cause** | Read errors, reproduce, check changes, gather evidence | Understand WHAT and WHY |\n| **2. Pattern** | Find working examples, compare | Identify differences |\n| **3. Hypothesis** | Form one theory, falsify minimally | Supported or replaced hypothesis |\n| **4. Implementation** | Establish reproduction, repair owner, verify invariant | Original symptom resolved with required evidence |\n\n## When Process Reveals \"No Root Cause\"\n\nIf systematic investigation reveals issue is truly environmental, timing-dependent, or external:\n\n1. You've completed the process\n2. Document what you investigated\n3. Implement appropriate handling (retry, timeout, error message)\n4. Add monitoring\u002Flogging for future investigation\n\n**But:** 95% of \"no root cause\" cases are incomplete investigation.\n\n## Supporting Techniques\n\nLoad these references only when the failure shape requires them:\n\n- [references\u002Froot-cause-tracing.md](references\u002Froot-cause-tracing.md) — trace a bad value or side effect backward to its originating owner.\n- [references\u002Fcondition-based-waiting.md](references\u002Fcondition-based-waiting.md) — diagnose timing\u002Fflakiness caused by arbitrary delays; use only when the task actually involves timing or explicitly authorized tests.\n","# Systematic Debugging\n\n## Overview\n\n**Core principle:** Find the root cause before attempting a repair. Do not patch the visible symptom while the responsible owner remains unknown.\n\nCausal Coding remains authoritative for mutation scope, testing authorization, verification cadence, and stopping. This Skill governs diagnosis: establish the visible failure, demonstrated mismatch, violated invariant, responsible owner, and a falsifiable repair hypothesis.\n\nTesting is opt-in. Debugging requires a reproducible symptom and falsifiable evidence, not automatically an automated test. Create, modify, or run tests only when the user, authoritative user-approved specification, or mandatory repository policy explicitly authorizes testing.\n\n## The Iron Law\n\n```\nNO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST\n```\n\nIf you haven't completed Phase 1, you cannot propose fixes.\n\n## The Four Phases\n\nYou MUST complete each phase before proceeding to the next.\n\n### Phase 1: Root Cause Investigation\n\n**BEFORE attempting ANY fix:**\n\n1. **Read Error Messages Carefully**\n   - Don't skip past errors or warnings\n   - They often contain the exact solution\n   - Read stack traces completely\n   - Note line numbers, file paths, error codes\n\n2. **Reproduce Consistently**\n   - Can you trigger it reliably?\n   - What are the exact steps?\n   - Does it happen every time?\n   - If not reproducible → gather more data, don't guess\n\n3. **Check Recent Changes**\n   - What changed that could cause this?\n   - Git diff, recent commits\n   - New dependencies, config changes\n   - Environmental differences\n\n4. **Gather Evidence in Multi-Component Systems**\n\n   **WHEN system has multiple components (CI → build → signing, API → service → database):**\n\n   **BEFORE proposing fixes, add diagnostic instrumentation:**\n   ```\n   For EACH component boundary:\n     - Log what data enters component\n     - Log what data exits component\n     - Verify environment\u002Fconfig propagation\n     - Check state at each layer\n\n   Run once to gather evidence showing WHERE it breaks\n   THEN analyze evidence to identify failing component\n   THEN investigate that specific component\n   ```\n\n   **Example (multi-layer system):**\n   ```bash\n   # Layer 1: Workflow\n   echo \"=== Secrets available in workflow: ===\"\n   echo \"IDENTITY: ${IDENTITY:+SET}${IDENTITY:-UNSET}\"\n\n   # Layer 2: Build script\n   echo \"=== Env vars in build script: ===\"\n   env | grep IDENTITY || echo \"IDENTITY not in environment\"\n\n   # Layer 3: Signing script\n   echo \"=== Keychain state: ===\"\n   security list-keychains\n   security find-identity -v\n\n   # Layer 4: Actual signing\n   codesign --sign \"$IDENTITY\" --verbose=4 \"$APP\"\n   ```\n\n   **This reveals:** Which layer fails (secrets → workflow ✓, workflow → build ✗)\n\n5. **Trace Data Flow**\n\n   **WHEN error is deep in call stack:**\n\n   Read [references\u002Froot-cause-tracing.md](references\u002Froot-cause-tracing.md) when the failure is deep in a call chain or the bad value's origin is unclear.\n\n   **Quick version:**\n   - Where does bad value originate?\n   - What called this with bad value?\n   - Keep tracing up until you find the source\n   - Fix at source, not at symptom\n\n### Phase 2: Pattern Analysis\n\n**Find the pattern before fixing:**\n\n1. **Find Working Examples**\n   - Locate similar working code in same codebase\n   - What works that's similar to what's broken?\n\n2. **Compare Against References**\n   - If an existing implementation or documented pattern governs the broken path, read the smallest relevant material that establishes its contract\n   - Expand only when a concrete unanswered question could change the diagnosis\n   - Understand the required pattern before applying it\n\n3. **Identify Differences**\n   - What's different between working and broken?\n   - List every difference, however small\n   - Don't assume \"that can't matter\"\n\n4. **Understand Dependencies**\n   - What other components does this need?\n   - What settings, config, environment?\n   - What assumptions does it make?\n\n### Phase 3: Hypothesis and Falsification\n\n**Scientific method:**\n\n1. **Form One Leading Hypothesis**\n   - State clearly: \"I think X is the root cause because Y\"\n   - Be specific and falsifiable\n   - Keep one leading hypothesis at a time\n\n2. **Falsify Minimally**\n   - Use the smallest observation, command, runtime probe, or reversible change that can disprove the hypothesis\n   - One variable at a time\n   - Do not stack candidate fixes\n   - An automated test is only one possible probe and still requires independent testing authorization\n\n3. **Evaluate Before Continuing**\n   - Supported? Proceed to Phase 4\n   - Contradicted? Return to the smallest reproduction and form a new hypothesis\n   - Do not add more fixes on top\n\n4. **When You Don't Know**\n   - Say \"I don't understand X\"\n   - Don't pretend to know\n   - Ask for help\n   - Research more\n\n### Phase 4: Implementation\n\n**Fix the root cause, not the symptom:**\n\n1. **Establish a Failing Reproduction**\n   - Use the simplest observable reproduction of the real symptom\n   - Prefer direct runtime\u002Finput\u002Foutput evidence when that is sufficient\n   - Use an automated test only when testing is explicitly authorized\n   - Do not create a one-off test script merely to manufacture a test requirement\n   - The reproduction must be capable of disproving the proposed fix\n\n2. **Implement Single Fix**\n   - Address the root cause identified\n   - ONE change at a time\n   - No \"while I'm here\" improvements\n   - No bundled refactoring\n\n3. **Verify Fix**\n   - Does the original reproduction now succeed?\n   - Is the violated invariant restored at the responsible boundary?\n   - Run tests only when testing is independently authorized; otherwise do not expand the validation surface just because a bug was fixed\n   - Use the completion-evidence workflow before claiming success\n\n4. **If the Repair Doesn't Work**\n   - STOP and return to the original reproduction\n   - If two repair attempts were based on the same causal hypothesis, do not make a third repair under that hypothesis\n   - Re-establish the mismatch and responsible owner from new evidence before another repair\n   - Do not stack patches merely because the previous one failed\n\n5. **Question Architecture Only When Evidence Requires It**\n\n   **Signals of an architectural problem:**\n   - distinct evidence-backed repairs repeatedly expose the same shared-state or coupling flaw across owners\n   - the responsible invariant cannot be restored without changing an actual architecture or public-contract boundary\n   - each local repair necessarily creates a new failure elsewhere\n\n   If the evidence now requires an architectural or public-contract decision, stop and surface that boundary before redesigning. Repeated failed guesses alone do not justify a rewrite.\n\n## Red Flags - STOP and Follow Process\n\nIf you catch yourself thinking:\n- \"Quick fix for now, investigate later\"\n- \"Just try changing X and see if it works\"\n- \"Add multiple changes and see what happens\"\n- \"Skip the reproduction; I'll just eyeball the fix\"\n- \"It's probably X, let me fix that\"\n- \"I don't fully understand but this might work\"\n- \"Pattern says X but I'll adapt it differently\"\n- \"Here are the main problems: [lists fixes without investigation]\"\n- Proposing solutions before tracing data flow\n- **\"One more fix attempt\" under a causal hypothesis that already failed twice**\n- **Each attempted repair reveals a different owner without new evidence**\n\n**ALL of these mean: STOP. Return to Phase 1.**\n\nQuestion architecture only when evidence establishes an architectural boundary, not merely because several guesses failed.\n\n## your human partner's Signals You're Doing It Wrong\n\n**Watch for these redirections:**\n- \"Is that not happening?\" - You assumed without verifying\n- \"Will it show us...?\" - You should have added evidence gathering\n- \"Stop guessing\" - You're proposing fixes without understanding\n- \"Ultra-think this\" - Question fundamentals, not just symptoms\n- \"We're stuck?\" (frustrated) - Your approach isn't working\n\n**When you see these:** STOP. Return to Phase 1.\n\n## Common Rationalizations\n\n| Excuse | Reality |\n|--------|---------|\n| \"Issue is simple, don't need process\" | Simple issues have root causes too. Process is fast for simple bugs. |\n| \"Emergency, no time for process\" | Systematic debugging is FASTER than guess-and-check thrashing. |\n| \"Just try this first, then investigate\" | First fix sets the pattern. Do it right from the start. |\n| \"I'll add a test because this is a bug fix\" | A bug fix requires a falsifiable reproduction; automated testing is separate and only in scope when independently authorized. |\n| \"Multiple fixes at once saves time\" | You cannot isolate what changed the outcome. Make one causal repair at a time. |\n| \"Reference too long, I'll adapt the pattern\" | Read the relevant contract and governing implementation closely enough to know which differences matter; do not substitute guesswork for evidence. |\n| \"I see the problem, let me fix it\" | Seeing symptoms ≠ understanding root cause. |\n| \"One more fix attempt\" under the same twice-failed hypothesis | Return to the original reproduction and establish a new evidence-backed hypothesis before another repair. |\n\n## Quick Reference\n\n| Phase | Key Activities | Success Criteria |\n|-------|---------------|------------------|\n| **1. Root Cause** | Read errors, reproduce, check changes, gather evidence | Understand WHAT and WHY |\n| **2. Pattern** | Find working examples, compare | Identify differences |\n| **3. Hypothesis** | Form one theory, falsify minimally | Supported or replaced hypothesis |\n| **4. Implementation** | Establish reproduction, repair owner, verify invariant | Original symptom resolved with required evidence |\n\n## When Process Reveals \"No Root Cause\"\n\nIf systematic investigation reveals issue is truly environmental, timing-dependent, or external:\n\n1. You've completed the process\n2. Document what you investigated\n3. Implement appropriate handling (retry, timeout, error message)\n4. Add monitoring\u002Flogging for future investigation\n\n**But:** 95% of \"no root cause\" cases are incomplete investigation.\n\n## Supporting Techniques\n\nLoad these references only when the failure shape requires them:\n\n- [references\u002Froot-cause-tracing.md](references\u002Froot-cause-tracing.md) — trace a bad value or side effect backward to its originating owner.\n- [references\u002Fcondition-based-waiting.md](references\u002Fcondition-based-waiting.md) — diagnose timing\u002Fflakiness caused by arbitrary delays; use only when the task actually involves timing or explicitly authorized tests.\n",{"name":5,"description":7},"main","59ee67804bc373a9bd079a3a27f47277a6efe564","skills\u002Fsystematic-debugging","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness","https:\u002F\u002Fgithub.com\u002Fham-zax","2026-11-15 01:18:51",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add ham-zax\u002Fwebharness --skill systematic-debugging",{"tool":36,"command":37},"bunx","bunx skills add ham-zax\u002Fwebharness --skill systematic-debugging",{"tool":39,"command":40},"pnpm","pnpm dlx skills add ham-zax\u002Fwebharness --skill systematic-debugging","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",true,[44,50,56,62,66,70],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"agents\u002Fopenai.yaml","REFERENCE","参考文档",288,"https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fsystematic-debugging\u002Fagents\u002Fopenai.yaml",{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"assets\u002Ficon.svg","ASSET","资产文件",1738,"https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fsystematic-debugging\u002Fassets\u002Ficon.svg",{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fcondition-based-waiting-example.ts","SCRIPT","脚本",5054,"https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fsystematic-debugging\u002Freferences\u002Fcondition-based-waiting-example.ts",{"path":63,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fcondition-based-waiting.md",3506,"https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fsystematic-debugging\u002Freferences\u002Fcondition-based-waiting.md",{"path":67,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Froot-cause-tracing.md",4519,"https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fsystematic-debugging\u002Freferences\u002Froot-cause-tracing.md",{"path":71,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":72,"sourceHtmlUrl":73},"scripts\u002Ffind-polluter.sh",1986,"https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fsystematic-debugging\u002Fscripts\u002Ffind-polluter.sh",[75,82,89,98,105,112],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7AS6BAQQ2WQJYS3WBNJPB2G","x-content","Create, rewrite, critique, select formats for, discover opportunities for, and learn from X\u002FTwitter content and X Articles for a technical AI-native developer\u002Fbuilder account. Use when turning ideas, source posts, releases, benchmarks, results, conversations, authenticated For You or creator-watch opportunities, or project evidence into an Original, Quote, Thread, Reply, or Article; reviewing article titles\u002Foutlines\u002Fvisual briefs\u002Flaunch hooks; improving drafts; choosing additive contributions from live X context; or learning from own-account outcomes. Own content intelligence only; compose with agent-browser for live X state and Growth OS for discovery provenance, approvals, measurement, and publication.","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fx-content\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7AS66FXQR8FEQYW8G8RJB2N","writing-plans","Create detailed implementation plans for multi-step software work before editing code. Use when requirements or a specification must become concrete file-level tasks, interfaces, acceptance criteria, risks, rollout, or explicitly required validation. Default to no test creation, test modification, test execution, TDD, regression-test, or coverage work unless the user, authoritative specification, or mandatory repository policy explicitly requires testing.","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7AS548FQ63SAB9G0X81VPGJ","skill-creator","Guide for creating and updating high-quality skills by translating workflows, conventions, and reusable processes into well-structured skills. Includes context, use case examples and spec for skills. Use this skill whenever a user asks to create, update, edit, improve, package, or troubleshoot a skill, and also for conversational questions about skills in ChatGPT (e.g., \"What are skills?\", \"What can I use skills for?\", \"What are the best skill use cases for me?\", \"Where can I find my skills?\").","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7AS4XD121Q85Y06EXRGYS4F","reflexion","Self-refinement, multi-perspective critique, verification, and durable lesson curation adapted from NeoLabHQ Reflexion. Use when the user asks to reflect, self-review, critique, double-check, verify and improve prior work, run a rigorous review, memorize lessons, or says \"then reflect\" after a coding, analysis, or writing task. Supports repository-aware evidence gathering and works without subagents or Claude hooks.","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Freflexion\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M7AS4RN5TYMA4P6SK6K7NVSR","ponytail","Enforce Ponytail's lazy-senior-developer approach for coding, fixing, refactoring, design, dependency choices, and explicit Ponytail modes such as review, audit, debt, gain, and help. Prefer YAGNI, existing code, standard library, native platform features, existing dependencies, low reader load, and the smallest correct diff. For source mutation, keep Causal Coding authoritative for scope, testing authorization, verification cadence, and stopping. On connected WSL\u002FLinux targets, compose with MCP Harness Router and use `wsl-web-harness` for authoritative repository work.","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":19},"01M7AS4H644231NR9E5WW3P91N","persistent-agent-loop","Use when one already-defined mission must remain active across extended waiting, repeated tool work, user steering, persistent processes, resumable checkpoints, or recovery after a lost model turn. Preserve mission continuity without treating pending waits, timers, idle periods, or subtask completion as mission completion. Do not use for multi-session decomposition or next-wave planning; use agent-work-planner for that. When implementation-affecting work is involved, preserve Causal Coding authority over mutation, testing, verification, continuation, and stopping. On connected WSL\u002FLinux targets, use mcp-harness-router to select concrete wsl-web-harness wait, Terminal, process, and repository primitives.","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fpersistent-agent-loop\u002FSKILL.md",[],[]]