[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FCVM79RAKNW18HAPTHP5NP":3,"skill-same:01M7FCVM79RAKNW18HAPTHP5NP":45},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":44},"01M7FCVM79RAKNW18HAPTHP5NP","principle-fix-root-causes",null,"Apply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a fix only when the state it handles is legitimate.","mr-jones123\u002Fpstack-harness","mr-jones123","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F104372691?v=4","01M7FCRJB8YVBWJJ1BQXH89H0R","Xynil Jhed Lacap","01M7FCRJBVNEVCP78T6XKNR907",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmr-jones123\u002Fpstack-harness\u002Fblob\u002Fmain\u002Fpi\u002Fskills\u002Fprinciple-fix-root-causes\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: principle-fix-root-causes\ndescription: \"Apply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a fix only when the state it handles is legitimate.\"\ndisable-model-invocation: true\n---\n\n# Fix Root Causes\n\nWhen debugging, fix the fault, not the place where it surfaced. The symptom is where a wrong state became visible. The root cause is the first place the system did something it should not do, or failed to handle a state it should handle.\n\n**Why:** A symptom fix hides the evidence and leaves the fault free to surface somewhere else. Each one makes the system harder to reason about, because the code now carries a workaround for a bug that nobody named.\n\n**Pattern:**\n- Reproduce first.\n- Ask \"why\" at each step until the answer is a wrong decision in the code, not a consequence of an earlier one.\n- When stuck, instrument. Read the actual error and the actual state. Do not guess.\n- Ask whether the state that triggered the symptom is legitimate. If the system may be in that state, the code that broke on it is the root cause, and handling the state there is the fix. If the state should never exist, a check where it broke hides the bug. Find what produced the state. Guards, retries, swallowed errors, clamped values, and discarded state are the usual ways to hide a bug.\n- When something fails only after a restart, suspect persisted state first: config files, caches, lock files, serialized state.\n- Check for the pattern, not just the instance. Find every place with the same fault and fix them all.\n- If a workaround needs a paragraph-long comment to justify it, the code is wrong. Fix the code, not the comment.\n- If the deciding fact took a deep dig to find, propose the cheap, always-on signal that would have shown it at first look.\n","# Fix Root Causes\n\nWhen debugging, fix the fault, not the place where it surfaced. The symptom is where a wrong state became visible. The root cause is the first place the system did something it should not do, or failed to handle a state it should handle.\n\n**Why:** A symptom fix hides the evidence and leaves the fault free to surface somewhere else. Each one makes the system harder to reason about, because the code now carries a workaround for a bug that nobody named.\n\n**Pattern:**\n- Reproduce first.\n- Ask \"why\" at each step until the answer is a wrong decision in the code, not a consequence of an earlier one.\n- When stuck, instrument. Read the actual error and the actual state. Do not guess.\n- Ask whether the state that triggered the symptom is legitimate. If the system may be in that state, the code that broke on it is the root cause, and handling the state there is the fix. If the state should never exist, a check where it broke hides the bug. Find what produced the state. Guards, retries, swallowed errors, clamped values, and discarded state are the usual ways to hide a bug.\n- When something fails only after a restart, suspect persisted state first: config files, caches, lock files, serialized state.\n- Check for the pattern, not just the instance. Find every place with the same fault and fix them all.\n- If a workaround needs a paragraph-long comment to justify it, the code is wrong. Fix the code, not the comment.\n- If the deciding fact took a deep dig to find, propose the cheap, always-on signal that would have shown it at first look.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","0826529c4391fc70aa5202aaf46321b52dd5fb0b","pi\u002Fskills\u002Fprinciple-fix-root-causes","https:\u002F\u002Fgithub.com\u002Fmr-jones123\u002Fpstack-harness","https:\u002F\u002Fgithub.com\u002Fmr-jones123","I make cool stuff.","2026-10-28 19:24:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add mr-jones123\u002Fpstack-harness --skill principle-fix-root-causes",{"tool":38,"command":39},"bunx","bunx skills add mr-jones123\u002Fpstack-harness --skill principle-fix-root-causes",{"tool":41,"command":42},"pnpm","pnpm dlx skills add mr-jones123\u002Fpstack-harness --skill principle-fix-root-causes","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmr-jones123\u002Fpstack-harness\u002Fblob\u002Fmain\u002Fpi\u002Fskills\u002Fprinciple-fix-root-causes\u002FSKILL.md",[],[46,53,60,67,73,80],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7FD55978EY23TE91WMB5N60","pstack-pi","Maps the Cursor names in pstack skills to Pi tools, child Pi processes, models, and paths. pstack skills read it once per session; poteto-mode embeds it.","https:\u002F\u002Fgithub.com\u002Fmr-jones123\u002Fpstack-harness\u002Fblob\u002Fmain\u002Fsrc\u002Fpi\u002Fskills\u002Fpstack-pi\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"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},"01M7FD534A9NNSPEF63NHQXKN9","create-skill","Author or revise an Agent Skills SKILL.md for Pi. Stands in for Cursor's built-in create-skill, which pstack skills name. Use when writing or editing a skill.","https:\u002F\u002Fgithub.com\u002Fmr-jones123\u002Fpstack-harness\u002Fblob\u002Fmain\u002Fsrc\u002Fpi\u002Fskills\u002Fcreate-skill\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7FD511C7R39T8T427JQ45FQ","pstack-omp","Maps the Cursor names in pstack skills to OMP tools, agents, models, and paths. pstack skills read it once per session; poteto-mode embeds it.","https:\u002F\u002Fgithub.com\u002Fmr-jones123\u002Fpstack-harness\u002Fblob\u002Fmain\u002Fsrc\u002Fomp\u002Fskills\u002Fpstack-omp\u002FSKILL.md",[],[],{"skillNo":68,"name":55,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7FD4YWGMPSRSNREJJ19QBCK","Author or revise an Agent Skills SKILL.md for OMP. Stands in for Cursor's built-in create-skill, which pstack skills name. Use when writing or editing a skill.","https:\u002F\u002Fgithub.com\u002Fmr-jones123\u002Fpstack-harness\u002Fblob\u002Fmain\u002Fsrc\u002Fomp\u002Fskills\u002Fcreate-skill\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7FD4T3R0XMZ7XYE96K36T9C","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002Fmr-jones123\u002Fpstack-harness\u002Fblob\u002Fmain\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7FD4P0A76YMSPZPKJY6VJKE","verify-this","Verify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED, NOT VERIFIED, or INCONCLUSIVE.","https:\u002F\u002Fgithub.com\u002Fmr-jones123\u002Fpstack-harness\u002Fblob\u002Fmain\u002Fskills\u002Fverify-this\u002FSKILL.md",[],[]]