[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DMFWAN6PN3FSG0KKS0CD0H":3,"skill-same:01M7DMFWAN6PN3FSG0KKS0CD0H":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":44},"01M7DMFWAN6PN3FSG0KKS0CD0H","principle-fix-root-causes",null,"调试时适用。把每个症状追溯到系统首次出错的地方并修复；只有守卫处理的状态确实合法时，守卫才算修复。","fenfenxu\u002Fpstack-zh","fenfenxu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2194243?v=4","01M7DMDSWBASX3NXC18FPHDJ8G","01M7DMDSWV8ASCZ4PH6YFXHPSJ",3,"MIT","https:\u002F\u002Fgithub.com\u002Ffenfenxu\u002Fpstack-zh\u002Fblob\u002Fmain\u002Fskills\u002Fprinciple-fix-root-causes\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: principle-fix-root-causes\ndescription: \"调试时适用。把每个症状追溯到系统首次出错的地方并修复；只有守卫处理的状态确实合法时，守卫才算修复。\"\ndisable-model-invocation: true\n---\n\n# 修复根因\n\n调试时，要修故障本身，而不是它暴露出来的位置。症状是错误状态显现出来的地方。根因是系统第一次做了不该做的事，或第一次没有处理本应处理的状态的地方。\n\n**原因：** 修复症状会掩盖证据，故障仍会在别处暴露。每修一次症状，系统就更难推理，因为代码里多了临时处理，却没人说清它针对哪个 bug。\n\n**模式：**\n- 先复现。\n- 在每一步都问「为什么」，直到答案指向代码里的错误决策，而不是更早决策造成的后果。\n- 卡住时就插桩。读取实际错误和实际状态。不要猜。\n- 先问触发症状的状态是否合法。如果系统可能处于这种状态，在这种状态下出错的代码就是根因，在那里处理这种状态就是修复。如果这种状态根本不应存在，在出错处加检查只会掩盖 bug。找出产生这种状态的代码。守卫、重试、吞掉错误、钳制数值和丢弃状态，都是常见的 bug 掩盖方式。\n- 只在重启后失败时，先怀疑持久化状态：配置文件、缓存、锁文件、序列化状态。\n- 查模式，不只查实例。找出所有存在相同故障的地方，一并修复。\n- 如果临时处理需要一长段注释才能自圆其说，代码就是错的。修代码，不是修注释。\n- 若决定性的事实要深挖才找得到，就提出一条便宜、一直开着的信号，让人第一眼就能看见它。\n","# 修复根因\n\n调试时，要修故障本身，而不是它暴露出来的位置。症状是错误状态显现出来的地方。根因是系统第一次做了不该做的事，或第一次没有处理本应处理的状态的地方。\n\n**原因：** 修复症状会掩盖证据，故障仍会在别处暴露。每修一次症状，系统就更难推理，因为代码里多了临时处理，却没人说清它针对哪个 bug。\n\n**模式：**\n- 先复现。\n- 在每一步都问「为什么」，直到答案指向代码里的错误决策，而不是更早决策造成的后果。\n- 卡住时就插桩。读取实际错误和实际状态。不要猜。\n- 先问触发症状的状态是否合法。如果系统可能处于这种状态，在这种状态下出错的代码就是根因，在那里处理这种状态就是修复。如果这种状态根本不应存在，在出错处加检查只会掩盖 bug。找出产生这种状态的代码。守卫、重试、吞掉错误、钳制数值和丢弃状态，都是常见的 bug 掩盖方式。\n- 只在重启后失败时，先怀疑持久化状态：配置文件、缓存、锁文件、序列化状态。\n- 查模式，不只查实例。找出所有存在相同故障的地方，一并修复。\n- 如果临时处理需要一长段注释才能自圆其说，代码就是错的。修代码，不是修注释。\n- 若决定性的事实要深挖才找得到，就提出一条便宜、一直开着的信号，让人第一眼就能看见它。\n",{"name":5,"description":7,"disable-model-invocation":23},true,"main","e4477188d43269545432a83e4ac5d0733a812d09","skills\u002Fprinciple-fix-root-causes",0,"https:\u002F\u002Fgithub.com\u002Ffenfenxu\u002Fpstack-zh","http:\u002F\u002Fpstack.ganhai.cloud","https:\u002F\u002Fgithub.com\u002Ffenfenxu","2026-10-21 12:14:41",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":23},[34,37,40],{"tool":35,"command":36},"npx","npx skills add fenfenxu\u002Fpstack-zh --skill principle-fix-root-causes",{"tool":38,"command":39},"bunx","bunx skills add fenfenxu\u002Fpstack-zh --skill principle-fix-root-causes",{"tool":41,"command":42},"pnpm","pnpm dlx skills add fenfenxu\u002Fpstack-zh --skill principle-fix-root-causes","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffenfenxu\u002Fpstack-zh\u002Fblob\u002Fmain\u002Fskills\u002Fprinciple-fix-root-causes\u002FSKILL.md",[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7DMHJV7QMEE1F43FFW98FV8","why","用于「为什么 X 是这样实现的」「为什么选了 Y」、设计理由、回归、事后复盘，或数据支撑的阈值问题。发现可用 MCP 并并行查询各证据类别（源码控制、工单跟踪、长文文档、实时聊天、基础设施可观测性、错误跟踪、产品分析数仓），然后返回带引用的决策与权衡解读。运行时行为请用 how。","https:\u002F\u002Fgithub.com\u002Ffenfenxu\u002Fpstack-zh\u002Fblob\u002Fmain\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M7DMHHRSS2SCZN6HWSANBJ35","unslop","从任意写作中剔除 AI 痕迹。","https:\u002F\u002Fgithub.com\u002Ffenfenxu\u002Fpstack-zh\u002Fblob\u002Fmain\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7DMHGFGH2YT86WQ6A53693W","typescript-best-practices","TypeScript 最佳实践。读取或编辑任意 .ts 或 .tsx 文件时使用。","https:\u002F\u002Fgithub.com\u002Ffenfenxu\u002Fpstack-zh\u002Fblob\u002Fmain\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7DMHEA1EGG2D9XQ33N66GDS","technical-writing","分层技术写作标准：Diátaxis 结构、Google 开发者风格句子、STE 指令规则、Global English 句法。用于 \u002Ftechnical-writing，或撰写\u002F审查文档、RFC、README、PR 描述、commit message 时。","https:\u002F\u002Fgithub.com\u002Ffenfenxu\u002Fpstack-zh\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7DMHCEXE1YRDR6XC1RXBG76","teach","用平实语言解释一段工作，让人真正理解。运行 how 与 why skill，把发现织成一份清晰说明。用于「teach me this」「help me really understand X」「explain this change or subsystem to me」。","https:\u002F\u002Fgithub.com\u002Ffenfenxu\u002Fpstack-zh\u002Fblob\u002Fmain\u002Fskills\u002Fteach\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7DMH9KNBP83SHAW4TGZ4713","tdd","仅当用户明确要求 TDD、失败测试或回归测试时使用，或 bug 有明显且廉价的本地测试目标时使用。测试路径不清、昂贵、偏集成或未要求时跳过。","https:\u002F\u002Fgithub.com\u002Ffenfenxu\u002Fpstack-zh\u002Fblob\u002Fmain\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]