[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M784YFC34HPS4VZB5B2Q4SR4":3,"skill-same:01M784YFC34HPS4VZB5B2Q4SR4":51},{"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":6,"updatedAt":30,"install":31,"resources":44},"01M784YFC34HPS4VZB5B2Q4SR4","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.","mhrsdev\u002FAI-Agent-Skills-Library","mhrsdev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F297913466?v=4","01M784VR2WC3PFWGB33RB1EVF9","MHRS","01M784VR3WX1XAH7SX6R2QZ99R",7,"MIT","https:\u002F\u002Fgithub.com\u002Fmhrsdev\u002FAI-Agent-Skills-Library\u002Fblob\u002Fmain\u002Forganized-skills\u002Fcode-quality-testing\u002Fmattpocock-skills\u002Fskills\u002Fdeprecated\u002Frequest-refactor-plan\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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.\n---\n\nThis skill will be invoked when the user wants to create a refactor request. You should go through the steps below. You may skip steps if you don't consider them necessary.\n\n1. Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions.\n\n2. Explore the repo to verify their assertions and understand the current state of the codebase.\n\n3. Ask whether they have considered other options, and present other options to them.\n\n4. Interview the user about the implementation. Be extremely detailed and thorough.\n\n5. Hammer out the exact scope of the implementation. Work out what you plan to change and what you plan not to change.\n\n6. Look in the codebase to check for test coverage of this area of the codebase. If there is insufficient test coverage, ask the user what their plans for testing are.\n\n7. Break the implementation into a plan of tiny commits. Remember Martin Fowler's advice to \"make each refactoring step as small as possible, so that you can always see the program working.\"\n\n8. Create a GitHub issue with the refactor plan. Use the following template for the issue description:\n\n\u003Crefactor-plan-template>\n\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\u003C\u002Frefactor-plan-template>\n","This skill will be invoked when the user wants to create a refactor request. You should go through the steps below. You may skip steps if you don't consider them necessary.\n\n1. Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions.\n\n2. Explore the repo to verify their assertions and understand the current state of the codebase.\n\n3. Ask whether they have considered other options, and present other options to them.\n\n4. Interview the user about the implementation. Be extremely detailed and thorough.\n\n5. Hammer out the exact scope of the implementation. Work out what you plan to change and what you plan not to change.\n\n6. Look in the codebase to check for test coverage of this area of the codebase. If there is insufficient test coverage, ask the user what their plans for testing are.\n\n7. Break the implementation into a plan of tiny commits. Remember Martin Fowler's advice to \"make each refactoring step as small as possible, so that you can always see the program working.\"\n\n8. Create a GitHub issue with the refactor plan. Use the following template for the issue description:\n\n\u003Crefactor-plan-template>\n\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\u003C\u002Frefactor-plan-template>\n",{"name":5,"description":7},"main","6d80f3aba1c1dd6c29729d8e3019577b9411126c","organized-skills\u002Fcode-quality-testing\u002Fmattpocock-skills\u002Fskills\u002Fdeprecated\u002Frequest-refactor-plan",0,"https:\u002F\u002Fgithub.com\u002Fmhrsdev\u002FAI-Agent-Skills-Library","https:\u002F\u002Fgithub.com\u002Fmhrsdev","2026-07-05 06:21:49",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add mhrsdev\u002FAI-Agent-Skills-Library --skill request-refactor-plan",{"tool":37,"command":38},"bunx","bunx skills add mhrsdev\u002FAI-Agent-Skills-Library --skill request-refactor-plan",{"tool":40,"command":41},"pnpm","pnpm dlx skills add mhrsdev\u002FAI-Agent-Skills-Library --skill request-refactor-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmhrsdev\u002FAI-Agent-Skills-Library\u002Fblob\u002Fmain\u002Forganized-skills\u002Fcode-quality-testing\u002Fmattpocock-skills\u002Fskills\u002Fdeprecated\u002Frequest-refactor-plan\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"README.md","REFERENCE","参考文档",2436,"https:\u002F\u002Fgithub.com\u002Fmhrsdev\u002FAI-Agent-Skills-Library\u002Fblob\u002Fmain\u002Forganized-skills\u002Fcode-quality-testing\u002Fmattpocock-skills\u002Fskills\u002Fdeprecated\u002Frequest-refactor-plan\u002FREADME.md",[52,59,65,72,79,86],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M785CANS10KGVX2B6JHZ2QX5","static-project-gallery-upload","Use when a user provides project\u002Fportfolio\u002Fgallery images for a static website and wants them displayed on the site, exact duplicate images removed, visually related building views kept together, images optimized, and a host upload folder such as \"UP FILE\" prepared. Triggers include Persian requests like \"عکس پروژه ها\", \"تکراری نباشن\", \"توی سایت نمایش داده بشن\", \"فایل های هاست\", \"UP FILE\".","https:\u002F\u002Fgithub.com\u002Fmhrsdev\u002FAI-Agent-Skills-Library\u002Fblob\u002Fmain\u002Forganized-skills\u002Fwebsite-business-builds\u002Fstatic-project-gallery-upload\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M785C3S56JQ75Y4QTPZWH9PG","contact-location-section","https:\u002F\u002Fgithub.com\u002Fmhrsdev\u002FAI-Agent-Skills-Library\u002Fblob\u002Fmain\u002Forganized-skills\u002Fwebsite-business-builds\u002Fcontact-location-section\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M785BWRPMZH26VQYVK3X4VY3","azerbaijan-website-build","Build premium tri-lingual websites from scratch for Azerbaijani businesses. Handles data gathering (website scrape, social media, or interview), brand development, and full Astro + Tailwind build with AZ\u002FRU\u002FEN language support.","https:\u002F\u002Fgithub.com\u002Fmhrsdev\u002FAI-Agent-Skills-Library\u002Fblob\u002Fmain\u002Forganized-skills\u002Fwebsite-business-builds\u002F07-azerbaijan-website-build\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M785BMQ7C9QPACPTVEPZ4C4X","local-business-rebuild","Build a stunning new website for a local business prospect. Adapted from the full website-rebuild skill but optimized for speculative local business pitches. 10-phase process: brand extraction, SEO audit, design audit, rebuild plan, full build with design system, copy optimization, combined QA, pre-deploy checklist, and output to monorepo. Uses scraped content from prospect-scrape as input. No tools\u002Fcalculator research phase. Single combined QA round. Triggers on: \"rebuild prospect\", \"local business rebuild\", \"build prospect site\", \"rebuild their site\", \"prospect rebuild\", or any request to build a new website for a qualified prospect.","https:\u002F\u002Fgithub.com\u002Fmhrsdev\u002FAI-Agent-Skills-Library\u002Fblob\u002Fmain\u002Forganized-skills\u002Fwebsite-business-builds\u002F06-local-business-rebuild\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M785BA38WMK2QEA9QBX3G201","website-rebuild","Full website rebuild agent. Takes an existing website URL and rebuilds it from scratch into a world-class, SEO-optimized, WCAG AA accessible, visually stunning website using Astro + Tailwind CSS, deployed to Vercel via GitHub. Executes a rigorous 14-phase process: brand extraction, content scraping, SEO audit, design audit, rebuild planning, full build with design system, copy optimization, 3 QA rounds, competitive tools research, tools build, tools QA, pre-deploy checklist, and Vercel deployment. Produces 11+ documentation deliverables. Triggers on: \"rebuild website\", \"redesign website\", \"rebuild site from URL\", \"website rebuild\", \"redo this website\", \"make this website better\", \"rebuild from scratch\", \"full site redesign\", or any request to take an existing URL and create a new, professional website from it. Also triggers when the user provides a URL and asks to build\u002Fcreate\u002Fdesign a new version of that site.","https:\u002F\u002Fgithub.com\u002Fmhrsdev\u002FAI-Agent-Skills-Library\u002Fblob\u002Fmain\u002Forganized-skills\u002Fwebsite-business-builds\u002F05-website-rebuild\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M785B6YDMSVJ30MTW6QDPME9","triage","Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.","https:\u002F\u002Fgithub.com\u002Fmhrsdev\u002FAI-Agent-Skills-Library\u002Fblob\u002Fmain\u002Forganized-skills\u002Fskill-authoring-meta\u002Ftriage\u002FSKILL.md",[],[]]