[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DJVB0KG0SRGDXEN7APX375":3,"skill-same:01M7DJVB0KG0SRGDXEN7APX375":54},{"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":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":28,"updatedAt":29,"install":30,"resources":43},"01M7DJVB0KG0SRGDXEN7APX375","maestro-code-review",null,"Use when a branch, pull request or changed code needs independent standards and specification review.","Orchestration-Maestro\u002Fmaestro-manifests","Orchestration-Maestro","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F322897002?v=4","01M7DJV5QYHV5358EX4AGZJZK3","01M7DJV5RPB4CBJZBKV9AHREM6",0,"MIT","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Fmanifests\u002Fcapabilities\u002Fpractice\u002Fmaestro-skills\u002Fskills\u002Fmaestro-code-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: maestro-code-review\ndescription: \"Use when a branch, pull request or changed code needs independent standards and specification review.\"\n---\n\n# Review a fixed diff on two axes\n\nResolve the supplied fixed point with `git rev-parse`, record `git diff \u003Cfixed-point>...HEAD` and the commit list,\nand reject an empty diff. Ask for a fixed point when none is supplied.\nFind the originating spec from issue references and the [tracker](..\u002F..\u002Freferences\u002Fissue-tracker.md), then an\nexplicit user path, then a matching repository spec. If none exists, ask; report “no spec available” when appropriate.\n\n## Standards sources and smell baseline\n\nRead the repository's rules, contribution guide, coding standards and domain vocabulary.\nRepository standards override these heuristics, which are judgement calls rather than automatic violations:\n\n| Smell | Possible remedy |\n| --- | --- |\n| Mysterious Name | Rename to expose the responsibility; investigate unclear design. |\n| Duplicated Code | Give one shared shape one owner and call it. |\n| Feature Envy | Move behaviour to the owner of the data it uses. |\n| Data Clumps | Give repeatedly travelling fields one named record. |\n| Primitive Obsession | Model a real domain concept instead of an unstructured primitive. |\n| Repeated Switches | Give repeated dispatch one map or polymorphic owner. |\n| Shotgun Surgery | Gather one change's scattered knowledge. |\n| Divergent Change | Separate responsibilities that change for unrelated reasons. |\n| Speculative Generality | Delete unused flexibility and hypothetical hooks. |\n| Message Chains | Hide a navigation walk behind its owner. |\n| Middle Man | Remove delegation that supplies no useful interface. |\n| Refused Bequest | Prefer composition when an implementation rejects its inherited contract. |\n\n## Independent passes\n\nRead tests before implementation. Compare what they prove with the contract; do not accept assertion count as\nbehaviour coverage. Run one inverted-condition experiment where feasible: if tests remain green after a meaningful\ncondition is reversed, identify the missing behavioural test. Be explicit about experiments you could not run.\n\nDispatch two fresh parallel `subagent` reviews using [REVIEWER](REVIEWER.md) and the\n[subagent brief](..\u002F..\u002Freferences\u002Fsubagents.md). Both receive the same fixed diff and commit list.\nStandards receives its source list and the complete smell baseline. Spec receives the actual originating contract.\nEach axis reports at most 400 words in chat. Present **Standards** and **Spec** separately; do not merge or rerank them.\nA standards pass cannot excuse the wrong feature, and a spec pass cannot excuse poor structure.\n\nPrefer structural remedies to another patch. Check dependency direction, canonical reuse and unnecessary public\nsurface. Ask why something was removed; unexplained removal is a finding, not an assumed cleanup.\nReport what cannot be verified from the diff rather than claiming a run you did not perform.\n\nGrade by [severity](..\u002F..\u002Freferences\u002Fseverity.md). Subsequent reviews use [RE-REVIEW](RE-REVIEW.md) and the fix diff,\nnot an expanding full audit. End with findings per axis and the worst severity within each axis, without a single winner.\n\nUse `\u002Fskill:maestro-documentation` as the documentation review lens. It owns the downstream\nprose pass; retain both review axes and the scope rules above.\n\nUse `\u002Fskill:maestro-security`, `\u002Fskill:maestro-performance` and `\u002Fskill:maestro-frontend-ui` as applicable\nreview lenses. Keep Standards and Spec independent; these lenses neither replace either pass nor turn an\nordinary review into a full security audit. The controller owns dispatch; a child reviewer reads the relevant\nlens and returns findings without starting children.\n","# Review a fixed diff on two axes\n\nResolve the supplied fixed point with `git rev-parse`, record `git diff \u003Cfixed-point>...HEAD` and the commit list,\nand reject an empty diff. Ask for a fixed point when none is supplied.\nFind the originating spec from issue references and the [tracker](..\u002F..\u002Freferences\u002Fissue-tracker.md), then an\nexplicit user path, then a matching repository spec. If none exists, ask; report “no spec available” when appropriate.\n\n## Standards sources and smell baseline\n\nRead the repository's rules, contribution guide, coding standards and domain vocabulary.\nRepository standards override these heuristics, which are judgement calls rather than automatic violations:\n\n| Smell | Possible remedy |\n| --- | --- |\n| Mysterious Name | Rename to expose the responsibility; investigate unclear design. |\n| Duplicated Code | Give one shared shape one owner and call it. |\n| Feature Envy | Move behaviour to the owner of the data it uses. |\n| Data Clumps | Give repeatedly travelling fields one named record. |\n| Primitive Obsession | Model a real domain concept instead of an unstructured primitive. |\n| Repeated Switches | Give repeated dispatch one map or polymorphic owner. |\n| Shotgun Surgery | Gather one change's scattered knowledge. |\n| Divergent Change | Separate responsibilities that change for unrelated reasons. |\n| Speculative Generality | Delete unused flexibility and hypothetical hooks. |\n| Message Chains | Hide a navigation walk behind its owner. |\n| Middle Man | Remove delegation that supplies no useful interface. |\n| Refused Bequest | Prefer composition when an implementation rejects its inherited contract. |\n\n## Independent passes\n\nRead tests before implementation. Compare what they prove with the contract; do not accept assertion count as\nbehaviour coverage. Run one inverted-condition experiment where feasible: if tests remain green after a meaningful\ncondition is reversed, identify the missing behavioural test. Be explicit about experiments you could not run.\n\nDispatch two fresh parallel `subagent` reviews using [REVIEWER](REVIEWER.md) and the\n[subagent brief](..\u002F..\u002Freferences\u002Fsubagents.md). Both receive the same fixed diff and commit list.\nStandards receives its source list and the complete smell baseline. Spec receives the actual originating contract.\nEach axis reports at most 400 words in chat. Present **Standards** and **Spec** separately; do not merge or rerank them.\nA standards pass cannot excuse the wrong feature, and a spec pass cannot excuse poor structure.\n\nPrefer structural remedies to another patch. Check dependency direction, canonical reuse and unnecessary public\nsurface. Ask why something was removed; unexplained removal is a finding, not an assumed cleanup.\nReport what cannot be verified from the diff rather than claiming a run you did not perform.\n\nGrade by [severity](..\u002F..\u002Freferences\u002Fseverity.md). Subsequent reviews use [RE-REVIEW](RE-REVIEW.md) and the fix diff,\nnot an expanding full audit. End with findings per axis and the worst severity within each axis, without a single winner.\n\nUse `\u002Fskill:maestro-documentation` as the documentation review lens. It owns the downstream\nprose pass; retain both review axes and the scope rules above.\n\nUse `\u002Fskill:maestro-security`, `\u002Fskill:maestro-performance` and `\u002Fskill:maestro-frontend-ui` as applicable\nreview lenses. Keep Standards and Spec independent; these lenses neither replace either pass nor turn an\nordinary review into a full security audit. The controller owns dispatch; a child reviewer reads the relevant\nlens and returns findings without starting children.\n",{"name":5,"description":7},"main","f33b1a1de12042270a260ffdddd74b67671a1d9a","manifests\u002Fcapabilities\u002Fpractice\u002Fmaestro-skills\u002Fskills\u002Fmaestro-code-review","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro","Automated guardrails for faster, better, more maintainable and more secure code. Our Northstar: never reached, always pursued.","2026-11-09 01:08:53",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add Orchestration-Maestro\u002Fmaestro-manifests --skill maestro-code-review",{"tool":36,"command":37},"bunx","bunx skills add Orchestration-Maestro\u002Fmaestro-manifests --skill maestro-code-review",{"tool":39,"command":40},"pnpm","pnpm dlx skills add Orchestration-Maestro\u002Fmaestro-manifests --skill maestro-code-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Fmanifests\u002Fcapabilities\u002Fpractice\u002Fmaestro-skills\u002Fskills\u002Fmaestro-code-review\u002FSKILL.md",true,[44,50],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"RE-REVIEW.md","REFERENCE","参考文档",667,"https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Fmanifests\u002Fcapabilities\u002Fpractice\u002Fmaestro-skills\u002Fskills\u002Fmaestro-code-review\u002FRE-REVIEW.md",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"REVIEWER.md",1522,"https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Fmanifests\u002Fcapabilities\u002Fpractice\u002Fmaestro-skills\u002Fskills\u002Fmaestro-code-review\u002FREVIEWER.md",[55,62,67,72,77,82],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M7DK0KB6JRRJRQPMXG075AQ6","audit","Fixture skill.","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Ftests\u002Fscorecard_cases\u002Fskill-without-name-takes-its-folder-name\u002Fmanifests\u002Fcapabilities\u002Fsecurity\u002Fscan\u002Fskills\u002Faudit\u002FSKILL.md",[],[],{"skillNo":63,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7DK0JAQG1J25DG064S7PR27","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Ftests\u002Fscorecard_cases\u002Fskill-without-name-takes-its-folder-name\u002Fmanifests\u002Fcapabilities\u002Fpractice\u002Freview\u002Fskills\u002Faudit\u002FSKILL.md",[],[],{"skillNo":68,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M7DK0HBNY88V2B7PF5E4JWZS","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Ftests\u002Fscorecard_cases\u002Fskill-with-empty-name-takes-its-folder-name\u002Fmanifests\u002Fcapabilities\u002Fsecurity\u002Fscan\u002Fskills\u002Faudit\u002FSKILL.md",[],[],{"skillNo":73,"name":57,"nameZh":6,"description":58,"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},"01M7DK0G9CB5MFGRD73SNEXXYE","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Ftests\u002Fscorecard_cases\u002Fskill-with-empty-name-takes-its-folder-name\u002Fmanifests\u002Fcapabilities\u002Fpractice\u002Freview\u002Fskills\u002Faudit\u002FSKILL.md",[],[],{"skillNo":78,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7DK0FA198RVD2KCEW9YDQ6K","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Ftests\u002Fscorecard_cases\u002Fskill-in-dot-folder-is-skipped\u002Fmanifests\u002Fcapabilities\u002Fpractice\u002Freview\u002Fskills\u002Faudit\u002FSKILL.md",[],[],{"skillNo":83,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M7DK0EAZVV9A5CN27PD2MTMB","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Ftests\u002Fscorecard_cases\u002Fskill-in-dot-folder-is-skipped\u002Fmanifests\u002Fcapabilities\u002Fpractice\u002Freview\u002Fskills\u002F.drafts\u002Faudit\u002FSKILL.md",[],[]]