[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MCWZ9VP4SCBVPMD5BKW3SK":3,"skill-same:01M6MCWZ9VP4SCBVPMD5BKW3SK":77},{"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":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6MCWZ9VP4SCBVPMD5BKW3SK","code-reviewer",null,"Review completed implementation batches for spec compliance and code quality. Invoke after execution batches complete, before merging, or when a review gate is reached in the workflow.","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\u002FMageByte-Zero\u002Fspec-superflow\u002Fskills\u002Fcode-reviewer\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"code","code reviewer","reviewer","when","review","invoke","review gate","for","batches","complete","gate","implementation","quality","execution","compliance","code quality","workflow","spec","2026-11-10 10:12:30",false,"---\nname: code-reviewer\ndescription: Review completed implementation batches for spec compliance and code quality. Invoke after execution batches complete, before merging, or when a review gate is reached in the workflow.\n---\n\n# Code Reviewer\n\n## Bundled runtime\n\nBefore executing a CLI line below, replace its leading `SSF` with `node \"\u003Cplugin-root>\u002Fscripts\u002Fspec-superflow.mjs\"`; `\u003Cplugin-root>` is the absolute directory two levels above this file. Never run `SSF` literally or call an `ssf` from `PATH`.\n\nTwo responsibilities: reviewing the recorded Git range and acting on findings with technical rigor. Review according to the persisted policy; verify feedback before implementing it.\n\n## Part 1: Requesting Review\n\n**Mandatory**: one whole-range review for Native `final`; one review per planned wave for `wave` and legacy plans. Avoid redundant per-task or final reviews of unchanged evidence.\n**Optional**: when stuck, before refactoring, after fixing complex bugs.\n\n### Procedure\n1. Get the review range from recorded execution evidence. For final review resolve the base in order: the recorded `state.review_base` start anchor, then the `review_base` in the recorded isolation context, then `git merge-base \u003Ctarget-branch> HEAD` for a legacy\u002Fmanual branch with an unambiguous target; head is `git rev-parse HEAD`. The CLI verifies this complete range. A failed final review retains the same base across fixes; wave repairs use the prior wave head. For a wave review use the recorded wave-start base. Never substitute `HEAD~1`; it misses earlier commits in multi-commit work.\n2. For Native `final`, the current executor reviews the complete diff locally and writes the report; do not dispatch a reviewer subagent. For user-authorized SDD with `wave` review, dispatch at most one reviewer for that wave using `skills\u002Fcode-reviewer\u002Fcode-reviewer-prompt.md`. If dispatch is unavailable, review locally.\n3. When dispatching, fill only `[DESCRIPTION]`, `[PLAN_OR_REQUIREMENTS]`, `[BASE_SHA]`, `[HEAD_SHA]`, `[WAVE_ID]`, and `[REVIEW_REPORT_FILE]`. Do not send the whole planning bundle.\n4. Write a non-empty report at `.superpowers\u002Fsdd\u002Freviews\u002F\u003Cwave-id>.md`, then record that path with `SSF execution review \u003Cchange-dir> --wave \u003Cwave-id> --base \u003Cbase-sha> --head \u003Chead-sha> --report .superpowers\u002Fsdd\u002Freviews\u002F\u003Cwave-id>.md --verdict \u003Cpass|fail>`.\nFor schema-2 plans, failed receipts also require `--issue \u003Cstable-finding-id>` for the blocking defect being repaired; reuse its ID across retries. Other findings keep their own IDs in the report. Identical failed input cannot consume another attempt.\n\n5. Critical\u002FImportant findings require a `fail` receipt, focused repair, one focused re-review, and replacement `pass`. Note Minor for later.\n6. At `adjudication-required`, wait for human authorization before another review.\n\n### Minimality And Scope\n\nFor unrequested complexity, cite the missing task requirement and diff line.\nUse Important for merge-blocking complexity and Minor for safe,\nbehavior-neutral redundancy; never score by line count.\n\n## Part 2: Receiving Review Feedback\n\n### The Response Pattern\n1. READ feedback without reacting\n2. UNDERSTAND and restate requirement\n3. VERIFY against codebase reality\n4. EVALUATE: technically sound for THIS codebase?\n5. RESPOND: technical acknowledgment or reasoned pushback\n6. IMPLEMENT: one item at a time, test each\n\n### Severity Levels\n\n| Level | Meaning | Action |\n|-------|---------|--------|\n| Critical | Bugs, security, data loss, broken functionality | Fix immediately |\n| Important | Architecture problems, missing features, poor error handling, test gaps | Fix before next batch |\n| Minor | Code style, optimization, documentation polish | Note for later |\n\n### Forbidden Responses\nNever: performative agreement (\"You're right!\", \"Great point!\"), blind implementation before verification, thanking the reviewer. Instead: restate the requirement, ask clarifying questions, push back with reasoning, or just fix it (actions > words).\n\n### Handling Unclear Feedback\nAsk only about unclear findings that change a material decision; continue independent, already-understood repairs within scope. Do not turn an unclear optional comment into a global stop.\n\n### Source-Specific Rules\n\n**From user**: Trusted — implement after understanding. Still ask if scope unclear. No performative agreement.\n\n**From external reviewer**: Before implementing, check: technically correct for this codebase? breaks existing functionality? reason for current implementation? works on all platforms? reviewer understands full context? If suggestion seems wrong, push back with technical reasoning.\n\n### When to Push Back\nSuggestion breaks existing functionality, reviewer lacks context, violates YAGNI, technically incorrect for this stack, legacy\u002Fcompatibility reasons, conflicts with user's architectural decisions. Push back with technical reasoning, not defensiveness.\n\n### Implementation Order\n1. Clarify only the material uncertainty that blocks a repair\n2. Fix blocking issues (breaks, security)\n3. Fix simple issues (typos, imports)\n4. Fix complex issues (refactoring, logic)\n5. Test each fix individually, verify no regressions\n\n## Common Mistakes\n\n| Mistake | Fix |\n|---------|-----|\n| Performative agreement | State requirement or just act |\n| Blind implementation | Verify against codebase first |\n| Batch without testing | One at a time, test each |\n| Proceeding without a wave receipt | Record `pass`\u002F`fail` via `SSF execution review` before the next dependent wave |\n| Assuming reviewer is right | Check if breaks things |\n| Avoiding pushback | Technical correctness > comfort |\n| Unclear feedback | Clarify the blocked finding while continuing independent repairs |\n\n## Exception Handling\n\n- **Parse failures**: Report specific file, request regenerated review package\n- **Missing files**: Regenerate via `scripts\u002Freview-package`. Empty diff = nothing to review\n- **User interruption**: Re-read review report on resume, continue from next unreviewed batch\n","# Code Reviewer\n\n## Bundled runtime\n\nBefore executing a CLI line below, replace its leading `SSF` with `node \"\u003Cplugin-root>\u002Fscripts\u002Fspec-superflow.mjs\"`; `\u003Cplugin-root>` is the absolute directory two levels above this file. Never run `SSF` literally or call an `ssf` from `PATH`.\n\nTwo responsibilities: reviewing the recorded Git range and acting on findings with technical rigor. Review according to the persisted policy; verify feedback before implementing it.\n\n## Part 1: Requesting Review\n\n**Mandatory**: one whole-range review for Native `final`; one review per planned wave for `wave` and legacy plans. Avoid redundant per-task or final reviews of unchanged evidence.\n**Optional**: when stuck, before refactoring, after fixing complex bugs.\n\n### Procedure\n1. Get the review range from recorded execution evidence. For final review resolve the base in order: the recorded `state.review_base` start anchor, then the `review_base` in the recorded isolation context, then `git merge-base \u003Ctarget-branch> HEAD` for a legacy\u002Fmanual branch with an unambiguous target; head is `git rev-parse HEAD`. The CLI verifies this complete range. A failed final review retains the same base across fixes; wave repairs use the prior wave head. For a wave review use the recorded wave-start base. Never substitute `HEAD~1`; it misses earlier commits in multi-commit work.\n2. For Native `final`, the current executor reviews the complete diff locally and writes the report; do not dispatch a reviewer subagent. For user-authorized SDD with `wave` review, dispatch at most one reviewer for that wave using `skills\u002Fcode-reviewer\u002Fcode-reviewer-prompt.md`. If dispatch is unavailable, review locally.\n3. When dispatching, fill only `[DESCRIPTION]`, `[PLAN_OR_REQUIREMENTS]`, `[BASE_SHA]`, `[HEAD_SHA]`, `[WAVE_ID]`, and `[REVIEW_REPORT_FILE]`. Do not send the whole planning bundle.\n4. Write a non-empty report at `.superpowers\u002Fsdd\u002Freviews\u002F\u003Cwave-id>.md`, then record that path with `SSF execution review \u003Cchange-dir> --wave \u003Cwave-id> --base \u003Cbase-sha> --head \u003Chead-sha> --report .superpowers\u002Fsdd\u002Freviews\u002F\u003Cwave-id>.md --verdict \u003Cpass|fail>`.\nFor schema-2 plans, failed receipts also require `--issue \u003Cstable-finding-id>` for the blocking defect being repaired; reuse its ID across retries. Other findings keep their own IDs in the report. Identical failed input cannot consume another attempt.\n\n5. Critical\u002FImportant findings require a `fail` receipt, focused repair, one focused re-review, and replacement `pass`. Note Minor for later.\n6. At `adjudication-required`, wait for human authorization before another review.\n\n### Minimality And Scope\n\nFor unrequested complexity, cite the missing task requirement and diff line.\nUse Important for merge-blocking complexity and Minor for safe,\nbehavior-neutral redundancy; never score by line count.\n\n## Part 2: Receiving Review Feedback\n\n### The Response Pattern\n1. READ feedback without reacting\n2. UNDERSTAND and restate requirement\n3. VERIFY against codebase reality\n4. EVALUATE: technically sound for THIS codebase?\n5. RESPOND: technical acknowledgment or reasoned pushback\n6. IMPLEMENT: one item at a time, test each\n\n### Severity Levels\n\n| Level | Meaning | Action |\n|-------|---------|--------|\n| Critical | Bugs, security, data loss, broken functionality | Fix immediately |\n| Important | Architecture problems, missing features, poor error handling, test gaps | Fix before next batch |\n| Minor | Code style, optimization, documentation polish | Note for later |\n\n### Forbidden Responses\nNever: performative agreement (\"You're right!\", \"Great point!\"), blind implementation before verification, thanking the reviewer. Instead: restate the requirement, ask clarifying questions, push back with reasoning, or just fix it (actions > words).\n\n### Handling Unclear Feedback\nAsk only about unclear findings that change a material decision; continue independent, already-understood repairs within scope. Do not turn an unclear optional comment into a global stop.\n\n### Source-Specific Rules\n\n**From user**: Trusted — implement after understanding. Still ask if scope unclear. No performative agreement.\n\n**From external reviewer**: Before implementing, check: technically correct for this codebase? breaks existing functionality? reason for current implementation? works on all platforms? reviewer understands full context? If suggestion seems wrong, push back with technical reasoning.\n\n### When to Push Back\nSuggestion breaks existing functionality, reviewer lacks context, violates YAGNI, technically incorrect for this stack, legacy\u002Fcompatibility reasons, conflicts with user's architectural decisions. Push back with technical reasoning, not defensiveness.\n\n### Implementation Order\n1. Clarify only the material uncertainty that blocks a repair\n2. Fix blocking issues (breaks, security)\n3. Fix simple issues (typos, imports)\n4. Fix complex issues (refactoring, logic)\n5. Test each fix individually, verify no regressions\n\n## Common Mistakes\n\n| Mistake | Fix |\n|---------|-----|\n| Performative agreement | State requirement or just act |\n| Blind implementation | Verify against codebase first |\n| Batch without testing | One at a time, test each |\n| Proceeding without a wave receipt | Record `pass`\u002F`fail` via `SSF execution review` before the next dependent wave |\n| Assuming reviewer is right | Check if breaks things |\n| Avoiding pushback | Technical correctness > comfort |\n| Unclear feedback | Clarify the blocked finding while continuing independent repairs |\n\n## Exception Handling\n\n- **Parse failures**: Report specific file, request regenerated review package\n- **Missing files**: Regenerate via `scripts\u002Freview-package`. Empty diff = nothing to review\n- **User interruption**: Re-read review report on resume, continue from next unreviewed batch\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FMageByte-Zero\u002Fspec-superflow\u002Fskills\u002Fcode-reviewer",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":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill code-reviewer",{"tool":63,"command":64},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill code-reviewer",{"tool":66,"command":67},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill code-reviewer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FMageByte-Zero\u002Fspec-superflow\u002Fskills\u002Fcode-reviewer\u002FSKILL.md",true,[71],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"code-reviewer-prompt.md","REFERENCE","参考文档",6777,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FMageByte-Zero\u002Fspec-superflow\u002Fskills\u002Fcode-reviewer\u002Fcode-reviewer-prompt.md",[78,88,96,104,112,120],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":87},"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":87},"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":87},"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":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":87},"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":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":87},"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":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":124,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":87},"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",[],[]]