[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71NSC8147WBP4X3PXWRD4P5":3,"skill-same:01M71NSC8147WBP4X3PXWRD4P5":70},{"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":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":13,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M71NSC8147WBP4X3PXWRD4P5","request-refactor-plan",null,"Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.","max-kharena\u002Fnous","max-kharena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F249811097?v=4","01M71NQQ2DRKPEV4AF9J318N31","01M71NQQ303XV5QX5DHCZKM41V",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Frequest-refactor-plan\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"request","refactor plan","refactor","request refactor plan","plan","interview","when","user interview","to plan","with","via","as","github issue","use","github","refactoring","commits","file","planning","create","2026-11-10 10:56:23",false,"---\nname: request-refactor-plan\ndescription: Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.\nversion: 0.1.0\ntype: planning\nrisk: medium\n---\n\n# Request Refactor Plan\n\nUse this skill when the user wants to create a refactor request. Skip steps only when they are clearly unnecessary.\n\n## Workflow\n\n1. Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions.\n2. Explore the repo to verify their assertions and understand the current state of the codebase.\n3. Ask whether they have considered other options, and present other options to them.\n4. Interview the user about the implementation. Be extremely detailed and thorough.\n5. Hammer out the exact scope: what will change and what will not change.\n6. Check test coverage for this area. If coverage is insufficient, ask the user what their testing plan is.\n7. Break the implementation into tiny commits. Follow Martin Fowler's advice: make each refactoring step as small as possible, so you can always see the program working.\n8. Create a GitHub issue with the refactor plan using `gh issue create`.\n\n## Scope Rules\n\n- Keep every proposed commit small enough to leave the codebase working.\n- Do not include specific file paths or code snippets in the final issue. They can become stale quickly.\n- Separate implementation decisions from testing decisions.\n- Make out-of-scope work explicit.\n\n## GitHub Issue Template\n\n```md\n## Problem Statement\n\nThe problem that the developer is facing, from the developer's perspective.\n\n## Solution\n\nThe solution to the problem, from the developer's perspective.\n\n## Commits\n\nA LONG, detailed implementation plan. Write the plan in plain English, breaking down the implementation into the tiniest commits possible. Each commit should leave the codebase in a working state.\n\n## Decision Document\n\nA list of implementation decisions that were made. This can include:\n\n- The modules that will be built\u002Fmodified\n- The interfaces of those modules that will be modified\n- Technical clarifications from the developer\n- Architectural decisions\n- Schema changes\n- API contracts\n- Specific interactions\n\nDo NOT include specific file paths or code snippets. They may end up being outdated very quickly.\n\n## Testing Decisions\n\nA list of testing decisions that were made. Include:\n\n- A description of what makes a good test (only test external behavior, not implementation details)\n- Which modules will be tested\n- Prior art for the tests (i.e. similar types of tests in the codebase)\n\n## Out of Scope\n\nA description of the things that are out of scope for this refactor.\n\n## Further Notes (optional)\n\nAny further notes about the refactor.\n```\n\n## Output Contract\n\nBefore creating the issue, show the user the final scope, tiny-commit plan, testing decisions, and out-of-scope list. After creating the issue, return the GitHub issue URL.\n","# Request Refactor Plan\n\nUse this skill when the user wants to create a refactor request. Skip steps only when they are clearly unnecessary.\n\n## Workflow\n\n1. Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions.\n2. Explore the repo to verify their assertions and understand the current state of the codebase.\n3. Ask whether they have considered other options, and present other options to them.\n4. Interview the user about the implementation. Be extremely detailed and thorough.\n5. Hammer out the exact scope: what will change and what will not change.\n6. Check test coverage for this area. If coverage is insufficient, ask the user what their testing plan is.\n7. Break the implementation into tiny commits. Follow Martin Fowler's advice: make each refactoring step as small as possible, so you can always see the program working.\n8. Create a GitHub issue with the refactor plan using `gh issue create`.\n\n## Scope Rules\n\n- Keep every proposed commit small enough to leave the codebase working.\n- Do not include specific file paths or code snippets in the final issue. They can become stale quickly.\n- Separate implementation decisions from testing decisions.\n- Make out-of-scope work explicit.\n\n## GitHub Issue Template\n\n```md\n## Problem Statement\n\nThe problem that the developer is facing, from the developer's perspective.\n\n## Solution\n\nThe solution to the problem, from the developer's perspective.\n\n## Commits\n\nA LONG, detailed implementation plan. Write the plan in plain English, breaking down the implementation into the tiniest commits possible. Each commit should leave the codebase in a working state.\n\n## Decision Document\n\nA list of implementation decisions that were made. This can include:\n\n- The modules that will be built\u002Fmodified\n- The interfaces of those modules that will be modified\n- Technical clarifications from the developer\n- Architectural decisions\n- Schema changes\n- API contracts\n- Specific interactions\n\nDo NOT include specific file paths or code snippets. They may end up being outdated very quickly.\n\n## Testing Decisions\n\nA list of testing decisions that were made. Include:\n\n- A description of what makes a good test (only test external behavior, not implementation details)\n- Which modules will be tested\n- Prior art for the tests (i.e. similar types of tests in the codebase)\n\n## Out of Scope\n\nA description of the things that are out of scope for this refactor.\n\n## Further Notes (optional)\n\nAny further notes about the refactor.\n```\n\n## Output Contract\n\nBefore creating the issue, show the user the final scope, tiny-commit plan, testing decisions, and out-of-scope list. After creating the issue, return the GitHub issue URL.\n",{"name":5,"risk":48,"type":41,"version":49,"description":7},"medium","0.1.0","main","05ddbcce9e3471b880e9edc7c63e4bdd40359861","skills\u002Frequest-refactor-plan","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous","https:\u002F\u002Fgithub.com\u002Fmax-kharena","2026-04-28 22:54:20",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add max-kharena\u002Fnous --skill request-refactor-plan",{"tool":62,"command":63},"bunx","bunx skills add max-kharena\u002Fnous --skill request-refactor-plan",{"tool":65,"command":66},"pnpm","pnpm dlx skills add max-kharena\u002Fnous --skill request-refactor-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Frequest-refactor-plan\u002FSKILL.md",true,[],[71,94,116,130,152,170],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":80,"publishedAt":43},"01M71NSZ170Z45TAP4CWY74YH3","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when the user wants to create, write, or build a new skill.","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[77],{"categoryNo":78,"categoryName":79,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[81,82,83,42,84,85,86,32,87,88,89,90,91,36,29,92,93],"write a skill","write","a skill","structure","build","new skill","user","new agent","resources","progressive","new","progressive disclosure","Meta",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":105,"publishedAt":43},"01M71NSX1D1C2MK3NJ42E1GQ47","verification-before-completion","Use when about to claim work is complete, fixed, passing, ready, merged, shippable, reviewed, or verified.","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[100],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[106,107,36,29,108,109,110,111,112,113,114,115],"verification","verification before completion","verified","claim","complete","quality","about","high","work","ready",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":43},"01M71NSVRTWNA5RYBRRRBQ4830","using-nous","Use when a request needs NOUS command routing or personality-driven planning.","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fusing-nous\u002FSKILL.md",[],[123,124,125,29,36,126,23,41,127,128,129],"using nous","personality","driven","command routing","command","routing","router",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":43},"01M71NST398KW57VNX72Z35MC2","using-git-worktrees","Use when NOUS execution needs isolated implementation branches, phase worktrees, parallel worktrees, or safe branch setup before executing a plan.","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fusing-git-worktrees\u002FSKILL.md",[],[137,138,139,140,141,142,143,144,145,113,27,146,29,36,147,148,149,150,151],"git","worktrees","git worktrees","using git worktrees","Using git","execution","branch setup","implementation","safe","phase","parallel worktrees","setup","branches","branch","parallel",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":43},"01M71NSRQ1VYJT15323W6HE1X1","ubiquitous-language","Use when the user wants to define domain terms, build a glossary, harden terminology, or extract a DDD-style ubiquitous language. Saves to UBIQUITOUS_LANGUAGE.md.","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fubiquitous-language\u002FSKILL.md",[],[159,160,161,162,85,163,164,165,36,87,166,167,168,29,169],"language","ubiquitous language","define","ddd","domain","style","terminology","extract","terms","harden","glossary",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":176,"publishedAt":43},"01M71NSPGTE0PY0YJ9HSDWB62B","triage-issue","Use when the user reports a bug and wants it investigated and filed as a durable GitHub issue with a TDD-based fix plan.","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Ftriage-issue\u002FSKILL.md",[],[177,178,179,35,87,180,181,111,182,37,27,32,183,29,36,184,34],"issue","triage issue","triage","it","bug","tdd","reports","fix"]