[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MM131T2FEECF35XYQ4EN34":3,"skill-same:01M6MM131T2FEECF35XYQ4EN34":72},{"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":23,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":65},"01M6MM131T2FEECF35XYQ4EN34","refactor",null,"Audit an existing project against its standards and apply selected improvements while preserving behavior.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1559,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freidemeister94\u002Fdevelopment-skills\u002Fskills\u002Frefactor\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33],"audit","write","edit","behavior","standards","focus","project","true","Existing","apply","2026-11-10 10:12:30",false,"---\nname: refactor\ndescription: \"Audit an existing project against its standards and apply selected improvements while preserving behavior.\"\nargument-hint: \"[focus]\"\nuser-invocable: true\ndisable-model-invocation: true\neffort: xhigh\ndisallowed-tools: Write Edit NotebookEdit\n---\n\n# Refactor\n\nBring an existing project closer to its standards without changing user-visible behavior.\nThis is the repository-convergence exception in the [development loop](..\u002F..\u002Fshared\u002Fdevelopment-loop.md).\nIt can inspect the whole target but can change only an approved tranche.\n\n`$ARGUMENTS` is a free-text focus, such as `database queries`, `src\u002Forders`, or a planned feature.\nWith a focus, audit that area and its required dependencies. Without one, audit the whole project.\nThe audit is always read-only. The user chooses what to change afterwards.\n\nThe audit changes nothing in the target.\nThe frontmatter withholds write tools during the audit, but the rule holds even when the harness exposes them.\n\n## 1. Audit\n\nApply the loop's Standards gate and the [engineering contract](..\u002F..\u002Fshared\u002Fengineering.md).\nRecord the source paths you selected.\n\nUse focused owners where their signal exists:\n\n- `align-docs` in inspection-only mode for repository context and documentation;\n- `staff-review` for code quality inside the scope.\n\nThen inspect what these owners do not cover.\nCheck the data model, query access paths, batching, indexes, repeated work, held resources, retries, recomputation, and behavior with multiple owners.\n\nExclude generated code and dependencies.\nRecord inspected surfaces and gaps.\nConfirm disputed library behavior in official documentation for the installed version.\n\nEvery finding includes evidence, location, [severity](..\u002F..\u002Fshared\u002Freview-categories.md), expected result, impact, effort, change risk, dependencies, confidence, and required proof.\n\n## 2. Rank\n\nDo not invent a score.\nPut security and data-loss risks before normal impact-to-effort ordering.\nSeverity measures defect risk. Impact over effort orders the roadmap.\n\nUse repository history to weight code that changes often.\nGroup findings with one root cause into one item.\nLabel each item `strong`, `worth exploring`, or `speculative`. Mark estimated values as estimates.\nDiagnose only. Do not design the fix yet.\n\n## 3. Choose\n\nPresent the roadmap, then ask the user to select tranches.\nSelecting none ends the work with the audit.\nA tranche covers one area, has compatible dependencies, and shares one verification and rollback strategy.\n\nA pure audit writes nothing.\nSave the roadmap under `docs\u002Fplans\u002F` only after the user selects work or explicitly asks to save it.\n\n## 4. Converge\n\nRun a full cycle for each tranche:\n\n1. Use `brainstorming` and `create-test` to settle invariants, thresholds, failure cases, and rollback.\n2. Capture a characterization proof that passes on unchanged code and after the refactor.\n3. Write the plan and chronicle, then present the plan for approval before code changes.\n4. Implement in small slices and run the nearest check after each slice.\n\nFinish with cumulative verification, independent review, and a recalculated roadmap.\nIf a tranche fails proof or review, stop and report it.\n\nKeep business changes as separate tasks.\nDo not widen a tranche during implementation. Record a new finding in the roadmap.\nNever commit.\n\n## 5. Resume\n\nThe saved roadmap and any incomplete tranche plan are the persistent state.\nA later run resumes them instead of repeating the audit.\n","# Refactor\n\nBring an existing project closer to its standards without changing user-visible behavior.\nThis is the repository-convergence exception in the [development loop](..\u002F..\u002Fshared\u002Fdevelopment-loop.md).\nIt can inspect the whole target but can change only an approved tranche.\n\n`$ARGUMENTS` is a free-text focus, such as `database queries`, `src\u002Forders`, or a planned feature.\nWith a focus, audit that area and its required dependencies. Without one, audit the whole project.\nThe audit is always read-only. The user chooses what to change afterwards.\n\nThe audit changes nothing in the target.\nThe frontmatter withholds write tools during the audit, but the rule holds even when the harness exposes them.\n\n## 1. Audit\n\nApply the loop's Standards gate and the [engineering contract](..\u002F..\u002Fshared\u002Fengineering.md).\nRecord the source paths you selected.\n\nUse focused owners where their signal exists:\n\n- `align-docs` in inspection-only mode for repository context and documentation;\n- `staff-review` for code quality inside the scope.\n\nThen inspect what these owners do not cover.\nCheck the data model, query access paths, batching, indexes, repeated work, held resources, retries, recomputation, and behavior with multiple owners.\n\nExclude generated code and dependencies.\nRecord inspected surfaces and gaps.\nConfirm disputed library behavior in official documentation for the installed version.\n\nEvery finding includes evidence, location, [severity](..\u002F..\u002Fshared\u002Freview-categories.md), expected result, impact, effort, change risk, dependencies, confidence, and required proof.\n\n## 2. Rank\n\nDo not invent a score.\nPut security and data-loss risks before normal impact-to-effort ordering.\nSeverity measures defect risk. Impact over effort orders the roadmap.\n\nUse repository history to weight code that changes often.\nGroup findings with one root cause into one item.\nLabel each item `strong`, `worth exploring`, or `speculative`. Mark estimated values as estimates.\nDiagnose only. Do not design the fix yet.\n\n## 3. Choose\n\nPresent the roadmap, then ask the user to select tranches.\nSelecting none ends the work with the audit.\nA tranche covers one area, has compatible dependencies, and shares one verification and rollback strategy.\n\nA pure audit writes nothing.\nSave the roadmap under `docs\u002Fplans\u002F` only after the user selects work or explicitly asks to save it.\n\n## 4. Converge\n\nRun a full cycle for each tranche:\n\n1. Use `brainstorming` and `create-test` to settle invariants, thresholds, failure cases, and rollback.\n2. Capture a characterization proof that passes on unchanged code and after the refactor.\n3. Write the plan and chronicle, then present the plan for approval before code changes.\n4. Implement in small slices and run the nearest check after each slice.\n\nFinish with cumulative verification, independent review, and a recalculated roadmap.\nIf a tranche fails proof or review, stop and report it.\n\nKeep business changes as separate tasks.\nDo not widen a tranche during implementation. Record a new finding in the roadmap.\nNever commit.\n\n## 5. Resume\n\nThe saved roadmap and any incomplete tranche plan are the persistent state.\nA later run resumes them instead of repeating the audit.\n",{"name":5,"effort":39,"description":7,"argument-hint":40,"user-invocable":41,"disallowed-tools":42,"disable-model-invocation":41},"xhigh","[focus]",true,"Write Edit NotebookEdit","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Freidemeister94\u002Fdevelopment-skills\u002Fskills\u002Frefactor",474,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-11 14:40:14",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":41},[55,58,61],{"tool":56,"command":57},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill refactor",{"tool":59,"command":60},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill refactor",{"tool":62,"command":63},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill refactor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freidemeister94\u002Fdevelopment-skills\u002Fskills\u002Frefactor\u002FSKILL.md",[66],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"agents\u002Fopenai.yaml","REFERENCE","参考文档",186,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freidemeister94\u002Fdevelopment-skills\u002Fskills\u002Frefactor\u002Fagents\u002Fopenai.yaml",[73,81,88,95,122,146],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":80},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"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":80},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\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":80},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":34},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","when","you","done","reviewer","io","change","cli","merge","past",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":34},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[129,130,131,117,132,133,134,135,136,137,138,139,140,141,107,142,30,143,144,145],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","session","end","reflection",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":161,"publishedAt":34},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[152,155,158],{"categoryNo":153,"categoryName":154,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":156,"categoryName":157,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":159,"categoryName":160,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[148,162,163,164,165,166,167,30,168,108,169,170,171,172,113,173,174,175,176,177],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]