[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CNR0TC1W8H2SC8GS3412D8":3,"skill-same:01M7CNR0TC1W8H2SC8GS3412D8":46},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7CNR0TC1W8H2SC8GS3412D8","systematic-debugging",null,"Systematic debugging and root cause analysis. Strictly forbids speculative code edits and guess-fixing.","arbasyaa\u002Fmy-pi-setup","arbasyaa","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F233517565?v=4","01M7CNHFSZRYGVHAPH9HAD7YF0","Arbasya Anandito","01M7CNHFTN4QAT1R8NRS4XRYTP",3,"MIT","https:\u002F\u002Fgithub.com\u002Farbasyaa\u002Fmy-pi-setup\u002Fblob\u002Fmain\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: systematic-debugging\ndescription: \"Systematic debugging and root cause analysis. Strictly forbids speculative code edits and guess-fixing.\"\n---\n\n# Systematic Debugging & Root Cause Analysis\n\n> Stop guessing. AI agents often jump straight to editing code based on assumptions, creating regressions and compound bugs. Follow this systematic 5-phase protocol for all debugging and bug-fixing tasks.\n\n---\n\n## The 5-Phase Debugging Protocol\n\n### Phase 1: Reproduce & Observe\n- **Do not touch production code yet.**\n- Reproduce the failure via a test case, minimal script, or terminal command.\n- Capture the exact error message, stack trace, and relevant log lines.\n- If reproduction isn't possible (e.g., environment-specific), explicitly state the reproduction barrier and analyze existing telemetry\u002Flogs.\n\n### Phase 2: Trace & Hypothesize\n- Trace data flow backwards from the point of failure to the input origin.\n- Formulate a single, testable hypothesis: *\"The error occurs because X receives Y when Z happens.\"*\n- Verify the hypothesis by inspecting state (logs, debugger, or code inspection) before changing any logic.\n\n### Phase 3: Root Cause Over Symptom Patching\n- **Fix the root cause, never just patch the symptom.**\n- If a function crashes on unexpected `null` \u002F `undefined`, determine **why** it was null instead of just slapping an optional chaining `?.` or fallback `|| {}`.\n- **Caller Audit:** Use `grep` \u002F codebase search to inspect **all callers** of any shared function you modify. Fixing only the path mentioned in a bug report leaves sibling callers broken.\n\n### Phase 4: Surgical Minimal Fix\n- Implement the smallest, cleanest fix that completely resolves the root cause.\n- Preserve existing architecture and conventions.\n- Do not refactor unrelated code or add unrequested dependencies in the name of a bug fix.\n\n### Phase 5: Verification & Regression Prevention\n- Re-run the reproduction step from Phase 1 to prove the fix works.\n- Run the project test suite and linter to ensure zero regressions.\n- When possible, write or update an automated unit\u002Fintegration test covering the edge case to prevent the bug from ever returning.\n","# Systematic Debugging & Root Cause Analysis\n\n> Stop guessing. AI agents often jump straight to editing code based on assumptions, creating regressions and compound bugs. Follow this systematic 5-phase protocol for all debugging and bug-fixing tasks.\n\n---\n\n## The 5-Phase Debugging Protocol\n\n### Phase 1: Reproduce & Observe\n- **Do not touch production code yet.**\n- Reproduce the failure via a test case, minimal script, or terminal command.\n- Capture the exact error message, stack trace, and relevant log lines.\n- If reproduction isn't possible (e.g., environment-specific), explicitly state the reproduction barrier and analyze existing telemetry\u002Flogs.\n\n### Phase 2: Trace & Hypothesize\n- Trace data flow backwards from the point of failure to the input origin.\n- Formulate a single, testable hypothesis: *\"The error occurs because X receives Y when Z happens.\"*\n- Verify the hypothesis by inspecting state (logs, debugger, or code inspection) before changing any logic.\n\n### Phase 3: Root Cause Over Symptom Patching\n- **Fix the root cause, never just patch the symptom.**\n- If a function crashes on unexpected `null` \u002F `undefined`, determine **why** it was null instead of just slapping an optional chaining `?.` or fallback `|| {}`.\n- **Caller Audit:** Use `grep` \u002F codebase search to inspect **all callers** of any shared function you modify. Fixing only the path mentioned in a bug report leaves sibling callers broken.\n\n### Phase 4: Surgical Minimal Fix\n- Implement the smallest, cleanest fix that completely resolves the root cause.\n- Preserve existing architecture and conventions.\n- Do not refactor unrelated code or add unrequested dependencies in the name of a bug fix.\n\n### Phase 5: Verification & Regression Prevention\n- Re-run the reproduction step from Phase 1 to prove the fix works.\n- Run the project test suite and linter to ensure zero regressions.\n- When possible, write or update an automated unit\u002Fintegration test covering the edge case to prevent the bug from ever returning.\n",{"name":5,"description":7},"main","a77e29f9fe4e5a5ee9cc856535ba243064ce91eb","skills\u002Fsystematic-debugging",0,"https:\u002F\u002Fgithub.com\u002Farbasyaa\u002Fmy-pi-setup","https:\u002F\u002Fgithub.com\u002Farbasyaa","Mahasiswa Teknik Informatika politeknik Negeri Cilacap","2026-10-29 12:35:34",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add arbasyaa\u002Fmy-pi-setup --skill systematic-debugging",{"tool":38,"command":39},"bunx","bunx skills add arbasyaa\u002Fmy-pi-setup --skill systematic-debugging",{"tool":41,"command":42},"pnpm","pnpm dlx skills add arbasyaa\u002Fmy-pi-setup --skill systematic-debugging","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Farbasyaa\u002Fmy-pi-setup\u002Fblob\u002Fmain\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"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},"01M7CNSESD7DRZ47PPA5Y59J8W","writing-shape","Writing, exploit: shape raw material into an article, paragraph by paragraph.","https:\u002F\u002Fgithub.com\u002Farbasyaa\u002Fmy-pi-setup\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-shape\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7CNSD0Y1KH71ZYSQY4ZP2PY","writing-fragments","Writing, explore: mine raw fragments, no structure yet.","https:\u002F\u002Fgithub.com\u002Farbasyaa\u002Fmy-pi-setup\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-fragments\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7CNSAWBPKXE2C0DBE0HE5YT","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Farbasyaa\u002Fmy-pi-setup\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7CNS93FZ4H60TYTNDVK0KH5","writing-beats","Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.","https:\u002F\u002Fgithub.com\u002Farbasyaa\u002Fmy-pi-setup\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-beats\u002FSKILL.md",[],[],{"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},"01M7CNS65S73NJ7GE8Y6YD4JEF","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Farbasyaa\u002Fmy-pi-setup\u002Fblob\u002Fmain\u002Fskills\u002Fwizard\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},"01M7CNS3XM180RKP39NMMXBET3","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Farbasyaa\u002Fmy-pi-setup\u002Fblob\u002Fmain\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[]]