[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79FZFBQCXK5G2HXAJAMVBVG":3,"skill-same:01M79FZFBQCXK5G2HXAJAMVBVG":52},{"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},"01M79FZFBQCXK5G2HXAJAMVBVG","request-refactor-plan",null,"通过用户访谈创建由微小提交组成的详细重构计划，然后将其作为 GitHub 事项提交。当用户想规划重构、创建重构 RFC，或将重构拆分为安全的增量步骤时使用。","15102045545\u002Fskills-cn","15102045545","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F168414493?v=4","01M79FZ671W8T1KPST7GRYEG3T","xiaokeer","01M79FZ67MMMDE1RZYSQGCPWK9",1,"MIT","https:\u002F\u002Fgithub.com\u002F15102045545\u002Fskills-cn\u002Fblob\u002Fmaster\u002Fskills\u002Fdeprecated\u002Frequest-refactor-plan\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: request-refactor-plan\ndescription: 通过用户访谈创建由微小提交组成的详细重构计划，然后将其作为 GitHub 事项提交。当用户想规划重构、创建重构 RFC，或将重构拆分为安全的增量步骤时使用。\n---\n\n当用户想创建重构请求时，会调用此技能。你应当完成以下步骤。如果认为某些步骤没有必要，可以跳过。\n\n1. 请用户详细说明想要解决的问题，并描述所有可能的解决思路。\n\n2. 探索仓库，验证用户的陈述并了解代码库当前状态。\n\n3. 询问用户是否考虑过其他选项，并向他们介绍其他选项。\n\n4. 围绕实现访谈用户。务必极其细致、全面。\n\n5. 反复推敲实现的确切范围。明确计划更改和计划不更改的内容。\n\n6. 检查代码库中该区域的测试覆盖率。如果测试覆盖不足，请询问用户的测试计划。\n\n7. 将实现拆分为由微小提交组成的计划。请牢记 Martin Fowler 的建议：“make each refactoring step as small as possible, so that you can always see the program working.”\n\n8. 创建包含重构计划的 GitHub 事项。事项描述使用以下模板：\n\n\u003Crefactor-plan-template>\n\n## 问题陈述\n\n从开发者视角描述其面临的问题。\n\n## 解决方案\n\n从开发者视角描述问题的解决方案。\n\n## 提交\n\n一份详尽的长篇实现计划。使用通俗语言编写计划，将实现拆分为尽可能小的提交。每次提交后，代码库都应当保持可用状态。\n\n## 决策文档\n\n列出已经作出的实现决策。可以包括：\n\n- 将要构建或修改的模块\n- 将要修改的模块接口\n- 开发者提供的技术澄清\n- 架构决策\n- Schema 变更\n- API 契约\n- 具体交互\n\n不得包含具体文件路径或代码片段。它们可能很快过时。\n\n## 测试决策\n\n列出已经作出的测试决策。包括：\n\n- 说明优秀测试的标准（只测试外部行为，不测试实现细节）\n- 将要测试哪些模块\n- 测试先例（即代码库中类似类型的测试）\n\n## 超出范围\n\n说明此次重构范围之外的内容。\n\n## 补充说明（可选）\n\n关于此次重构的任何补充说明。\n\n\u003C\u002Frefactor-plan-template>\n","当用户想创建重构请求时，会调用此技能。你应当完成以下步骤。如果认为某些步骤没有必要，可以跳过。\n\n1. 请用户详细说明想要解决的问题，并描述所有可能的解决思路。\n\n2. 探索仓库，验证用户的陈述并了解代码库当前状态。\n\n3. 询问用户是否考虑过其他选项，并向他们介绍其他选项。\n\n4. 围绕实现访谈用户。务必极其细致、全面。\n\n5. 反复推敲实现的确切范围。明确计划更改和计划不更改的内容。\n\n6. 检查代码库中该区域的测试覆盖率。如果测试覆盖不足，请询问用户的测试计划。\n\n7. 将实现拆分为由微小提交组成的计划。请牢记 Martin Fowler 的建议：“make each refactoring step as small as possible, so that you can always see the program working.”\n\n8. 创建包含重构计划的 GitHub 事项。事项描述使用以下模板：\n\n\u003Crefactor-plan-template>\n\n## 问题陈述\n\n从开发者视角描述其面临的问题。\n\n## 解决方案\n\n从开发者视角描述问题的解决方案。\n\n## 提交\n\n一份详尽的长篇实现计划。使用通俗语言编写计划，将实现拆分为尽可能小的提交。每次提交后，代码库都应当保持可用状态。\n\n## 决策文档\n\n列出已经作出的实现决策。可以包括：\n\n- 将要构建或修改的模块\n- 将要修改的模块接口\n- 开发者提供的技术澄清\n- 架构决策\n- Schema 变更\n- API 契约\n- 具体交互\n\n不得包含具体文件路径或代码片段。它们可能很快过时。\n\n## 测试决策\n\n列出已经作出的测试决策。包括：\n\n- 说明优秀测试的标准（只测试外部行为，不测试实现细节）\n- 将要测试哪些模块\n- 测试先例（即代码库中类似类型的测试）\n\n## 超出范围\n\n说明此次重构范围之外的内容。\n\n## 补充说明（可选）\n\n关于此次重构的任何补充说明。\n\n\u003C\u002Frefactor-plan-template>\n",{"name":5,"description":7},"master","a7a44e6effe5a404eb8b622483896d79904f0c69","skills\u002Fdeprecated\u002Frequest-refactor-plan",0,"https:\u002F\u002Fgithub.com\u002F15102045545\u002Fskills-cn","https:\u002F\u002Fgithub.com\u002F15102045545","软件开发工程师","2026-07-23 11:44:15",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add 15102045545\u002Fskills-cn --skill request-refactor-plan",{"tool":38,"command":39},"bunx","bunx skills add 15102045545\u002Fskills-cn --skill request-refactor-plan",{"tool":41,"command":42},"pnpm","pnpm dlx skills add 15102045545\u002Fskills-cn --skill request-refactor-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F15102045545\u002Fskills-cn\u002Fblob\u002Fmaster\u002Fskills\u002Fdeprecated\u002Frequest-refactor-plan\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",99,"https:\u002F\u002Fgithub.com\u002F15102045545\u002Fskills-cn\u002Fblob\u002Fmaster\u002Fskills\u002Fdeprecated\u002Frequest-refactor-plan\u002Fagents\u002Fopenai.yaml",[53,60,67,74,81,88],{"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},"01M79G19FBV713ADE9Q95Y4D8E","writing-great-skills","出色编写和编辑技能的参考资料——让技能具备可预测性的词汇与原则。","https:\u002F\u002Fgithub.com\u002F15102045545\u002Fskills-cn\u002Fblob\u002Fmaster\u002Fskills\u002Fproductivity\u002Fwriting-great-skills\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},"01M79G1888W4AQP8N9D2X0XYV4","teach","在此工作区内向用户教授新的技能或概念。","https:\u002F\u002Fgithub.com\u002F15102045545\u002Fskills-cn\u002Fblob\u002Fmaster\u002Fskills\u002Fproductivity\u002Fteach\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M79G15Z3NX0EJBP03A6VC3GJ","handoff","将当前对话压缩成交接文档，以便另一个智能体接手。","https:\u002F\u002Fgithub.com\u002F15102045545\u002Fskills-cn\u002Fblob\u002Fmaster\u002Fskills\u002Fproductivity\u002Fhandoff\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M79G14SKDFSWTADQZMQSCN9Q","grilling","围绕计划、决策或想法对用户进行不留情面的深度追问。当用户想对自己的思路进行压力测试，或使用任何“深度追问”触发措辞时使用。","https:\u002F\u002Fgithub.com\u002F15102045545\u002Fskills-cn\u002Fblob\u002Fmaster\u002Fskills\u002Fproductivity\u002Fgrilling\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M79G12NEZDVFGG45SP50P37Q","grill-me","通过不留情面的深度追问打磨计划或设计。","https:\u002F\u002Fgithub.com\u002F15102045545\u002Fskills-cn\u002Fblob\u002Fmaster\u002Fskills\u002Fproductivity\u002Fgrill-me\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M79G1198KAG4PE1YADT2G30R","obsidian-vault","使用 wikilink 和索引笔记搜索、创建和管理 Obsidian 仓库中的笔记。当用户想要在 Obsidian 中查找、创建或整理笔记时使用。","https:\u002F\u002Fgithub.com\u002F15102045545\u002Fskills-cn\u002Fblob\u002Fmaster\u002Fskills\u002Fpersonal\u002Fobsidian-vault\u002FSKILL.md",[],[]]