[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DMF8KXW2DS67X8P5EFH4W0":3,"skill-same:01M7DMF8KXW2DS67X8P5EFH4W0":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},"01M7DMF8KXW2DS67X8P5EFH4W0","no-comments",null,"开出 Comment Sicko，修掉接受的 finding，并为注释里声称的约束提出用代码落实的办法。","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\u002Fno-comments\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: no-comments\ndescription: \"开出 Comment Sicko，修掉接受的 finding，并为注释里声称的约束提出用代码落实的办法。\"\ndisable-model-invocation: true\n---\n\n# No comments\n\n开出 Comment Sicko。按接受的 finding 去做。\n\n以 Comment Sicko 不带成见的眼光为准。\n\n## 范围\n\n用调用方给的文件或 diff。没有的话，就用当前分支相对基础分支（默认 `main`）的 diff，包括工作区里没提交的改动。\n\n## 步骤\n\n1. 用 `Task` 开一个 `subagent_type: \"comment-sicko\"` 的子代理。把范围传给它。按这项工作给每个子代理选推理强度，以及用 fast 还是标准速度，见 **poteto-mode** skill 的 Subagents 一节。不要复述它的规则。\n2. 检查它的报告和 diff。以下这些要拒掉：改了应用代码、超出范围、删掉了受例外保护的注释、`MUST KILL` 给的理由不对，以及把刻意保留的代码当成罪证的标记。针对我们自己代码里出人意料之处、要求改结构的标记，仍然算要处理，不要把那些注释恢复回来。一条 keep 只有在能证明它说的是我们改不了的东西时才成立。检查范围内有没有漏掉的 lint 和 TypeScript 抑制注释。涉及正确性或安全的抑制注释，仍然是要处理的 `MUST KILL`。只有符合确切的例外、并有范围内的证明时，才恢复被删的注释。在接受理由单薄的 `IMPORTANT` 或 `do not remove` 的 kill 或 keep 之前，对它们涉及的符号跑一遍 `\u002Fhow` 或 `\u002Fwhy`。kill 拿不准时，不恢复。keep 被驳倒或仍然拿不准时，删掉它。拒掉一份报告后，撤销它的改动，点明哪里不对，重跑一次。第二份再被拒，就报告为未解决，并让 `\u002Fno-comments` 失败。\n3. 简单的已接受标记直接修：删掉死路径、去掉一个参数，或者改用真正的 API。只要有一处修法需要先定形态，就对接受的这一批标记和周边代码跑一次 `\u002Farchitect`。停在草图这一步。architect 负责定形态，第 4 步负责实现。\n4. 在范围内做最小的根因修复。去掉每一个点了名的 workaround。根因在范围外时，合入范围内最小的修复，其余的报告为未解决。**principle-fix-root-causes** 和 **principle-redesign-from-first-principles** 这两个 skill 只用来指导意图。两者都不允许你扩大范围，也不允许你去修范围外的同类问题。绝不在症状上加防护补丁。\n5. 约束类注释写的是 `do not remove`、`do not change wording` 或 `talk to X before changing`。说的是我们改不了的东西的 keep，留着。为其余的约束提出范围内成本最低的落实办法：类型、运行时检查、测试或 CI 里的 lint。交互场景下等用户批准。无人值守和 eval 场景需要调用方事先批准。批准了，就先用代码落实，再删注释。没批准，就删掉注释，把这条约束报告为未解决，并为范围外的工作画个草图。\n6. 报告：删了多少条、恢复了哪些注释、重跑了几次、architect 的草图、做了哪些修复、提出了哪些落实办法、落实了哪些、哪些约束没有强制、还有哪些未解决的工作。\n","# No comments\n\n开出 Comment Sicko。按接受的 finding 去做。\n\n以 Comment Sicko 不带成见的眼光为准。\n\n## 范围\n\n用调用方给的文件或 diff。没有的话，就用当前分支相对基础分支（默认 `main`）的 diff，包括工作区里没提交的改动。\n\n## 步骤\n\n1. 用 `Task` 开一个 `subagent_type: \"comment-sicko\"` 的子代理。把范围传给它。按这项工作给每个子代理选推理强度，以及用 fast 还是标准速度，见 **poteto-mode** skill 的 Subagents 一节。不要复述它的规则。\n2. 检查它的报告和 diff。以下这些要拒掉：改了应用代码、超出范围、删掉了受例外保护的注释、`MUST KILL` 给的理由不对，以及把刻意保留的代码当成罪证的标记。针对我们自己代码里出人意料之处、要求改结构的标记，仍然算要处理，不要把那些注释恢复回来。一条 keep 只有在能证明它说的是我们改不了的东西时才成立。检查范围内有没有漏掉的 lint 和 TypeScript 抑制注释。涉及正确性或安全的抑制注释，仍然是要处理的 `MUST KILL`。只有符合确切的例外、并有范围内的证明时，才恢复被删的注释。在接受理由单薄的 `IMPORTANT` 或 `do not remove` 的 kill 或 keep 之前，对它们涉及的符号跑一遍 `\u002Fhow` 或 `\u002Fwhy`。kill 拿不准时，不恢复。keep 被驳倒或仍然拿不准时，删掉它。拒掉一份报告后，撤销它的改动，点明哪里不对，重跑一次。第二份再被拒，就报告为未解决，并让 `\u002Fno-comments` 失败。\n3. 简单的已接受标记直接修：删掉死路径、去掉一个参数，或者改用真正的 API。只要有一处修法需要先定形态，就对接受的这一批标记和周边代码跑一次 `\u002Farchitect`。停在草图这一步。architect 负责定形态，第 4 步负责实现。\n4. 在范围内做最小的根因修复。去掉每一个点了名的 workaround。根因在范围外时，合入范围内最小的修复，其余的报告为未解决。**principle-fix-root-causes** 和 **principle-redesign-from-first-principles** 这两个 skill 只用来指导意图。两者都不允许你扩大范围，也不允许你去修范围外的同类问题。绝不在症状上加防护补丁。\n5. 约束类注释写的是 `do not remove`、`do not change wording` 或 `talk to X before changing`。说的是我们改不了的东西的 keep，留着。为其余的约束提出范围内成本最低的落实办法：类型、运行时检查、测试或 CI 里的 lint。交互场景下等用户批准。无人值守和 eval 场景需要调用方事先批准。批准了，就先用代码落实，再删注释。没批准，就删掉注释，把这条约束报告为未解决，并为范围外的工作画个草图。\n6. 报告：删了多少条、恢复了哪些注释、重跑了几次、architect 的草图、做了哪些修复、提出了哪些落实办法、落实了哪些、哪些约束没有强制、还有哪些未解决的工作。\n",{"name":5,"description":7,"disable-model-invocation":23},true,"main","e4477188d43269545432a83e4ac5d0733a812d09","skills\u002Fno-comments",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 no-comments",{"tool":38,"command":39},"bunx","bunx skills add fenfenxu\u002Fpstack-zh --skill no-comments",{"tool":41,"command":42},"pnpm","pnpm dlx skills add fenfenxu\u002Fpstack-zh --skill no-comments","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffenfenxu\u002Fpstack-zh\u002Fblob\u002Fmain\u002Fskills\u002Fno-comments\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",[],[]]