[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MJG2XHKYGRB0JKFE90QMB9":3,"skill-same:01M6MJG2XHKYGRB0JKFE90QMB9":75},{"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":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6MJG2XHKYGRB0JKFE90QMB9","maintainability-review",null,"Review code changes only for maintainability risks: unnecessary complexity, poor readability, duplication, weak separation of concerns, and misalignment with repository conventions. Use when the user explicitly asks for maintainability review, code quality review, clean code review, complexity review, readability review, simplification review, or how to simplify changed code without changing behavior.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fmimfort\u002Frag_for_git\u002Fplugin\u002Fskills\u002Fmaintainability-review\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"review","maintainability review","maintainability","code quality review","code review","when","separation","separation of concerns","how to","simplification","readability","quality review","duplication","clean","complexity","only","how","simplify","clean code","repository","code","code quality","2026-11-10 10:12:30",false,"---\nname: maintainability-review\ndescription: \"Review code changes only for maintainability risks: unnecessary complexity, poor readability, duplication, weak separation of concerns, and misalignment with repository conventions. Use when the user explicitly asks for maintainability review, code quality review, clean code review, complexity review, readability review, simplification review, or how to simplify changed code without changing behavior.\"\n---\n\n# Maintainability Review\n\n\u003C!-- include: _common\u002Fdimension-scope.md -->\n\n\u003C!-- include: _common\u002Ftool-usage.md -->\n\u003C!-- include: _common\u002Freviewer-grounding.md -->\nIn `rag-reviewer:review-pr` use the PR-session tools above. Standalone (no PR session): use\nthe session-less tools per the reviewer-grounding block when reviewer is connected and the\nindex is fresh; otherwise fall back to grep\u002FRead.\n\n## Goal\n\nLook only for maintainability risks in the selected changes. Ignore performance,\nsecurity, and general correctness unless they directly explain a maintainability\nconcern.\n\nPrioritize findings such as:\n\n- unnecessary branching, flag combinations, and deep nesting that increase cognitive\n  load;\n- large or mixed-responsibility functions that became harder to understand;\n- duplication or near-duplication that should likely be consolidated;\n- abstractions, wrappers, or indirection layers that hide a simple flow without a\n  clear payoff;\n- hidden side effects, implicit contracts, or unclear data flow;\n- naming or structure that materially harms readability or makes intent harder to\n  recover;\n- changes that drift away from established repository patterns or documented\n  contributor rules;\n- behavior changes that should likely carry nearby tests according to project\n  practice;\n- edits to generated artifacts when the repository expects source changes plus\n  regeneration.\n\n## Repository Context\n\nBefore raising project-practice findings, read the repository-local guidance that\ngoverns the current workspace.\n\nPrefer this order:\n\n1. In `rag-reviewer:review-pr`, read `CLAUDE.md` or `AGENTS.md` via `read_file`; in standalone,\n   read them from disk.\n2. Read the nearby implementation to understand existing patterns.\n3. Compare the change against the established local style before flagging it.\n\nDo not treat personal preference as a project convention.\n\n## Method\n\n1. Read the diff first.\n2. Open only the nearby code needed to understand the changed path.\n3. Prefer concrete maintainability costs over vague \"clean code\" opinions.\n4. State assumptions explicitly when a finding depends on local context.\n5. Suggest a simpler alternative that preserves behavior and better fits local\n   patterns; put this in the `suggestion` field.\n6. Avoid review spam. Do not invent nits.\n\n## Simplification Heuristics\n\nPrefer suggestions such as:\n\n- split a mixed-responsibility function into a small orchestration layer plus focused\n  helpers;\n- replace deeply nested conditionals with guard clauses or flatter control flow;\n- collapse pass-through wrappers that add little or no meaning;\n- replace duplicated branches with a shared helper or data-driven mapping;\n- move side-effect-free transformation logic closer together and isolate I\u002FO\n  boundaries;\n- reuse established project helpers, managers, or patterns instead of introducing\n  ad-hoc flow;\n- keep changes local when a broader abstraction is not justified by the diff.\n\nDo not suggest refactors that increase indirection without a clear readability win.\n\n## What Not To Flag\n\nDo not raise findings for:\n\n- purely stylistic preferences when the code is already clear;\n- unchanged legacy code outside the requested review scope;\n- hypothetical future abstractions with no present need;\n- formatter or linter nits that are already handled automatically;\n- rename suggestions unless the current naming materially impairs understanding.\n\n## Severity\n\n- `critical` \u002F `high`: the change introduces major complexity, unclear control flow,\n  or strong convention drift that is likely to cause future bugs or make the code\n  meaningfully harder to modify safely.\n- `medium`: the change adds noticeable complexity or weakens readability or\n  consistency enough that it should probably be simplified before merge.\n- `low`: the change is acceptable but has a worthwhile simplification or cleanup\n  opportunity.\n\n## Output\n\nReturn only actionable findings.\n\nReturn ONLY the findings JSON used by the review pipeline, with\n`\"category\": \"maintainability\"`:\n\n\u003C!-- include: _common\u002Ffindings-schema.md -->\n- Calibrate `confidence` against concrete, grounded evidence: a duplicated block you can quote\n  or a real complexity hotspot → 0.8+; a subjective readability concern → 0.5–0.7; pure taste\n  → ≤ 0.4 (drop).\nSet \"category\" to \"maintainability\"; \"side\" is always \"RIGHT\".\n\nThe `suggestion` field replaces what in the original Codex format appeared after\n`Simplification:` — put the concrete simplifying alternative there.\n\n\u003C!-- include: _common\u002Fdimension-output-tail.md -->\n","# Maintainability Review\n\n\u003C!-- include: _common\u002Fdimension-scope.md -->\n\n\u003C!-- include: _common\u002Ftool-usage.md -->\n\u003C!-- include: _common\u002Freviewer-grounding.md -->\nIn `rag-reviewer:review-pr` use the PR-session tools above. Standalone (no PR session): use\nthe session-less tools per the reviewer-grounding block when reviewer is connected and the\nindex is fresh; otherwise fall back to grep\u002FRead.\n\n## Goal\n\nLook only for maintainability risks in the selected changes. Ignore performance,\nsecurity, and general correctness unless they directly explain a maintainability\nconcern.\n\nPrioritize findings such as:\n\n- unnecessary branching, flag combinations, and deep nesting that increase cognitive\n  load;\n- large or mixed-responsibility functions that became harder to understand;\n- duplication or near-duplication that should likely be consolidated;\n- abstractions, wrappers, or indirection layers that hide a simple flow without a\n  clear payoff;\n- hidden side effects, implicit contracts, or unclear data flow;\n- naming or structure that materially harms readability or makes intent harder to\n  recover;\n- changes that drift away from established repository patterns or documented\n  contributor rules;\n- behavior changes that should likely carry nearby tests according to project\n  practice;\n- edits to generated artifacts when the repository expects source changes plus\n  regeneration.\n\n## Repository Context\n\nBefore raising project-practice findings, read the repository-local guidance that\ngoverns the current workspace.\n\nPrefer this order:\n\n1. In `rag-reviewer:review-pr`, read `CLAUDE.md` or `AGENTS.md` via `read_file`; in standalone,\n   read them from disk.\n2. Read the nearby implementation to understand existing patterns.\n3. Compare the change against the established local style before flagging it.\n\nDo not treat personal preference as a project convention.\n\n## Method\n\n1. Read the diff first.\n2. Open only the nearby code needed to understand the changed path.\n3. Prefer concrete maintainability costs over vague \"clean code\" opinions.\n4. State assumptions explicitly when a finding depends on local context.\n5. Suggest a simpler alternative that preserves behavior and better fits local\n   patterns; put this in the `suggestion` field.\n6. Avoid review spam. Do not invent nits.\n\n## Simplification Heuristics\n\nPrefer suggestions such as:\n\n- split a mixed-responsibility function into a small orchestration layer plus focused\n  helpers;\n- replace deeply nested conditionals with guard clauses or flatter control flow;\n- collapse pass-through wrappers that add little or no meaning;\n- replace duplicated branches with a shared helper or data-driven mapping;\n- move side-effect-free transformation logic closer together and isolate I\u002FO\n  boundaries;\n- reuse established project helpers, managers, or patterns instead of introducing\n  ad-hoc flow;\n- keep changes local when a broader abstraction is not justified by the diff.\n\nDo not suggest refactors that increase indirection without a clear readability win.\n\n## What Not To Flag\n\nDo not raise findings for:\n\n- purely stylistic preferences when the code is already clear;\n- unchanged legacy code outside the requested review scope;\n- hypothetical future abstractions with no present need;\n- formatter or linter nits that are already handled automatically;\n- rename suggestions unless the current naming materially impairs understanding.\n\n## Severity\n\n- `critical` \u002F `high`: the change introduces major complexity, unclear control flow,\n  or strong convention drift that is likely to cause future bugs or make the code\n  meaningfully harder to modify safely.\n- `medium`: the change adds noticeable complexity or weakens readability or\n  consistency enough that it should probably be simplified before merge.\n- `low`: the change is acceptable but has a worthwhile simplification or cleanup\n  opportunity.\n\n## Output\n\nReturn only actionable findings.\n\nReturn ONLY the findings JSON used by the review pipeline, with\n`\"category\": \"maintainability\"`:\n\n\u003C!-- include: _common\u002Ffindings-schema.md -->\n- Calibrate `confidence` against concrete, grounded evidence: a duplicated block you can quote\n  or a real complexity hotspot → 0.8+; a subjective readability concern → 0.5–0.7; pure taste\n  → ≤ 0.4 (drop).\nSet \"category\" to \"maintainability\"; \"side\" is always \"RIGHT\".\n\nThe `suggestion` field replaces what in the original Codex format appeared after\n`Simplification:` — put the concrete simplifying alternative there.\n\n\u003C!-- include: _common\u002Fdimension-output-tail.md -->\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fmimfort\u002Frag_for_git\u002Fplugin\u002Fskills\u002Fmaintainability-review",491,"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-14 14:06:13",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill maintainability-review",{"tool":67,"command":68},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill maintainability-review",{"tool":70,"command":71},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill maintainability-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fmimfort\u002Frag_for_git\u002Fplugin\u002Fskills\u002Fmaintainability-review\u002FSKILL.md",true,[],[76,86,94,102,110,118],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":85},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"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":80,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":85},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":85},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":85},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":85},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":122,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":85},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]