[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASVGPQSCJA3VRVTH8FTT7K":3,"skill-same:01M7ASVGPQSCJA3VRVTH8FTT7K":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"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":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7ASVGPQSCJA3VRVTH8FTT7K","refactoring",null,"Refactoring process. Invoke immediately when user or document mentions refactoring, or proactively when code gets too complex or messy.","saski\u002Farnesto","saski","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F140356?v=4","01M7ASBDSNXTRYDYB4K1PEA1RV","01M7ASBDTAKBDAAV99S1GE7HK6",6,"Unlicense","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frefactoring\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: refactoring\ndescription: Refactoring process. Invoke immediately when user or document mentions refactoring, or proactively when code gets too complex or messy.\n---\n\n# Refactoring Production Code\n\nSTARTER_CHARACTER = 🟣\n\nWhen starting, announce: \"🟣 Using REFACTORING skill\".\n\nWork autonomously as much as possible. Start with the simplest thing or file and proceed to the more complex ones.\n\n## Stages\n\n1. Prep\n2. Main Refactoring\n3. Final Evaluation\n4. Summary\n\n## Test Code Policy\n\nDo not change test code during refactoring, except:\n- Renames that follow production code renames (imports, function calls)\n- Import path updates if something moved\n\nNever change test assertions, test data, or test logic.\n\n## 1. Prep\n\n- Determine scope: use specified files, or identify related files (imports, shared functionality), or ask user\n- Add files in scope to todo list\n- Find or create .\u002Ftest.sh, verify all tests pass\n- Remove comments from files in scope (commit per file)\n\n## 2. Main Refactoring\n\n### Code Style\n\nPrefer self-explanatory, readable code over comments.\n\n- Use functional helper methods for clarity\n- Remove dead code\n- Extract paragraphs into methods\n- Use better variable names\n- Remove unused imports\n- Remove unhelpful local variables\n- Look for opportunities to simplify\n- Use domain language - name things for what they ARE, not how they're implemented\n- Keep consistent abstraction levels within methods\n\n### Process\n\nFor each refactor:\n1. Ensure all tests pass\n2. Choose and perform the simplest possible refactoring (one at a time)\n3. Ensure all tests pass after the change\n4. Commit each successful refactor with the message format: \"- r \u003Crefactoring>\" (the message must include the \"- r\" prefix)\n   Prefer small granular commits. If applying the same refactoring pattern to multiple locations, change one location at a time and commit each separately.\n5. Provide a status update after each refactor\n\n## 3. Final Evaluation\n\nWhen you see no more obvious refactoring opportunities, say \"🔍 Entering final evaluation.\"\n\nShift focus: you've been implementing. Now become a critic. Your job is to find problems, not produce code.\n\nRe-read Code Style guidelines. Look at each file in scope. Consider blind spots - what improvements haven't we even considered that would make the code better, easier, more maintainable?\n\nFor each file, find ONE thing that could be better. If you find something:\n1. Fix it using the same refactoring process (test, change, test, commit)\n2. Look again; fixing one thing often reveals the next\n\nRepeat until you find nothing more to improve.\n\n## 4. Summary\n\nProvide a high-level summary of the refactoring:\n- List each file that was touched\n- Describe the key improvements made in each file\n\n## Language-Specific\n\nFor Java: See [references\u002Fjava.md](references\u002Fjava.md)\n","# Refactoring Production Code\n\nSTARTER_CHARACTER = 🟣\n\nWhen starting, announce: \"🟣 Using REFACTORING skill\".\n\nWork autonomously as much as possible. Start with the simplest thing or file and proceed to the more complex ones.\n\n## Stages\n\n1. Prep\n2. Main Refactoring\n3. Final Evaluation\n4. Summary\n\n## Test Code Policy\n\nDo not change test code during refactoring, except:\n- Renames that follow production code renames (imports, function calls)\n- Import path updates if something moved\n\nNever change test assertions, test data, or test logic.\n\n## 1. Prep\n\n- Determine scope: use specified files, or identify related files (imports, shared functionality), or ask user\n- Add files in scope to todo list\n- Find or create .\u002Ftest.sh, verify all tests pass\n- Remove comments from files in scope (commit per file)\n\n## 2. Main Refactoring\n\n### Code Style\n\nPrefer self-explanatory, readable code over comments.\n\n- Use functional helper methods for clarity\n- Remove dead code\n- Extract paragraphs into methods\n- Use better variable names\n- Remove unused imports\n- Remove unhelpful local variables\n- Look for opportunities to simplify\n- Use domain language - name things for what they ARE, not how they're implemented\n- Keep consistent abstraction levels within methods\n\n### Process\n\nFor each refactor:\n1. Ensure all tests pass\n2. Choose and perform the simplest possible refactoring (one at a time)\n3. Ensure all tests pass after the change\n4. Commit each successful refactor with the message format: \"- r \u003Crefactoring>\" (the message must include the \"- r\" prefix)\n   Prefer small granular commits. If applying the same refactoring pattern to multiple locations, change one location at a time and commit each separately.\n5. Provide a status update after each refactor\n\n## 3. Final Evaluation\n\nWhen you see no more obvious refactoring opportunities, say \"🔍 Entering final evaluation.\"\n\nShift focus: you've been implementing. Now become a critic. Your job is to find problems, not produce code.\n\nRe-read Code Style guidelines. Look at each file in scope. Consider blind spots - what improvements haven't we even considered that would make the code better, easier, more maintainable?\n\nFor each file, find ONE thing that could be better. If you find something:\n1. Fix it using the same refactoring process (test, change, test, commit)\n2. Look again; fixing one thing often reveals the next\n\nRepeat until you find nothing more to improve.\n\n## 4. Summary\n\nProvide a high-level summary of the refactoring:\n- List each file that was touched\n- Describe the key improvements made in each file\n\n## Language-Specific\n\nFor Java: See [references\u002Fjava.md](references\u002Fjava.md)\n",{"name":5,"description":7},"main","3c24fc2c035029b08c7326774bee3fef8fb95566",".agents\u002Fskills\u002Frefactoring",0,"https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto","https:\u002F\u002Fgithub.com\u002Fsaski","http:\u002F\u002Fsaski.com","2026-11-12 20:09:16",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add saski\u002Farnesto --skill refactoring",{"tool":37,"command":38},"bunx","bunx skills add saski\u002Farnesto --skill refactoring",{"tool":40,"command":41},"pnpm","pnpm dlx skills add saski\u002Farnesto --skill refactoring","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frefactoring\u002FSKILL.md",true,[45,51],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"credits.md","REFERENCE","参考文档",185,"https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frefactoring\u002Fcredits.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fjava.md",114,"https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frefactoring\u002Freferences\u002Fjava.md",[56,63,70,77,84,91],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M7AT7F5FSHNAMFMF01N0QA1X","visualize","Use \u002Fvisualize for creating compact charts, diagrams, or other visuals inline as part of the conversation itself. It chooses among Markdown tables, Mermaid, inline HTML, and other supported in-transcript forms. Use Canvas for durable artifacts outside the transcript that users may revisit, refine, or share.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fvisualize\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M7AT79MHSAR3JDDMP7DGERM9","update-cursor-settings","Modify Cursor\u002FVSCode user settings in settings.json. Use when you want to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fupdate-cursor-settings\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M7AT73WF3Y22E0FKYAMCCJES","update-cli-config","View and modify Cursor CLI configuration settings in ~\u002F.cursor\u002Fcli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fupdate-cli-config\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M7AT6F3FBP85AJJ5BJNR8B5W","statusline","Configure a custom status line in the CLI. Use when the user mentions status line, statusline, statusLine, CLI status bar, prompt footer customization, or wants to add session context above the prompt.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fstatusline\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M7AT6D24QFS5XRAFN8S5XJ7W","split-to-prs","Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fsplit-to-prs\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M7AT69FYFN84XZKW452JV5DF","shell","Runs the rest of a \u002Fshell request as a literal shell command. Use only when the user explicitly invokes \u002Fshell and wants the following text executed directly in the terminal.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fshell\u002FSKILL.md",[],[]]