[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6R61V2K7VHGETXGGET3KBXE":3,"skill-same:01M6R61V2K7VHGETXGGET3KBXE":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":27,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":13,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M6R61V2K7VHGETXGGET3KBXE","code-review",null,"Review changes since a fixed point along two axes, Standards and Spec, reported side by side. Use when reviewing a branch, a PR, or work in progress.","r3dlex\u002Fskills","r3dlex","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F291373160?v=4","01M6PEFNGGBVB7SHAPWXFFX933","01M6R5SDWFHT94734KJFMYE1SX",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fr3dlex\u002Fskills\u002Fblob\u002Fmain\u002F04-validate-handoff\u002Fcode-review\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[28,29,30,31,32,33,34,35,36,37,38,39,40,41],"code review","review","code","spec","pr","review changes","work","branch","use","standards","progress","changes","point","when","2026-11-10 10:12:30",false,"---\nname: code-review\ndescription: 'Review changes since a fixed point along two axes, Standards and Spec, reported side by side. Use when reviewing a branch, a PR, or work in progress.'\n---\n\n# Code Review\n\nTwo-axis review of the diff between `HEAD` and a fixed point the user supplies:\n\n- **Standards** — does the code conform to this repo's documented coding standards?\n- **Spec** — does the code faithfully implement the originating issue or spec?\n\nRun the two axes **independently**, in separate workers where the harness allows, so neither\npollutes the other's context. Then aggregate.\n\n## Process\n\n### 1. Pin the fixed point\n\nWhatever the user said is the fixed point — a commit SHA, branch name, tag, `main`, `HEAD~5`.\nIf they did not specify one, ask.\n\nCapture the diff once: `git diff \u003Cfixed-point>...HEAD` (three-dot, so the comparison is\nagainst the merge-base), plus `git log \u003Cfixed-point>..HEAD --oneline`.\n\nConfirm the fixed point resolves (`git rev-parse \u003Cfixed-point>`) and the diff is non-empty\n**before** going further. A bad ref or empty diff must fail here, not inside two workers.\n\n### 2. Identify the spec source\n\nIn order: issue references in the commit messages (`#123`, `Closes #45`); a path the user\npassed as an argument; a spec file under `docs\u002F`, `specs\u002F`, or the repo's scratch area\nmatching the branch or feature. Use `to-issues` to resolve a hosted reference, and only when\na tracker is configured and authorized.\n\nIf nothing is found, ask. If the user says there is no spec, the Spec axis reports\n\"no spec available\" rather than inventing one.\n\n### 3. Identify the standards sources\n\nAnything documenting how code should be written here — `CODING_STANDARDS.md`,\n`CONTRIBUTING.md`, `AGENTS.md`, `CONTEXT.md`.\n\nOn top of that, the Standards axis always carries the **smell baseline** in\n[SMELL-BASELINE.md](SMELL-BASELINE.md), which applies even when a repo documents nothing.\nTwo rules bind it: **the repo overrides** (a documented standard always wins, and where it\nendorses something the baseline would flag, suppress the smell), and **every smell is a\njudgement call** — a labelled heuristic, never a hard violation. Skip anything tooling\nalready enforces.\n\n### 4. Run both axes\n\n**Standards brief** — give it the diff command, the commit list, the standards sources\nfound, and the smell baseline **pasted in full** (the worker has no other access to it).\nAsk for: every place the diff violates a documented standard, citing the file and rule; and\nany baseline smell, named with the hunk quoted. Distinguish hard violations from judgement\ncalls — documented breaches can be hard, baseline smells never are. Under 400 words.\n\n**Spec brief** — give it the diff command, the commit list, and the spec. Ask for:\nrequirements the spec asked for that are missing or partial; behaviour in the diff nobody\nasked for (scope creep); and requirements that look implemented but implemented wrongly.\nQuote the spec line for each finding. Under 400 words.\n\nIf there is no spec, skip the Spec axis and say so in the report.\n\n### 5. Aggregate\n\nPresent both reports under `## Standards` and `## Spec`, verbatim or lightly cleaned. Do\n**not** merge or rerank findings across axes.\n\nEnd with one line: total findings per axis, and the worst issue *within each axis*. Do not\npick a single winner across axes — that is exactly the reranking the separation prevents.\n\n## Why two axes\n\nA change can pass one and fail the other:\n\n- Follows every standard but implements the wrong thing → **Standards pass, Spec fail.**\n- Does exactly what the issue asked but breaks the project's conventions → **Spec pass,\n  Standards fail.**\n\nReporting them separately stops one axis from masking the other.\n\nEnd by declaring knowledge kind `review`, then reading\n[ai-catapult-init\u002Fmodules\u002Fknowledge-publish.md](..\u002Fai-catapult-init\u002Fmodules\u002Fknowledge-publish.md) and running its host-neutral producer step — publish when a registry exists, otherwise record `unpublished: \u003Creason>`; never fail the skill because of the registry.\n","# Code Review\n\nTwo-axis review of the diff between `HEAD` and a fixed point the user supplies:\n\n- **Standards** — does the code conform to this repo's documented coding standards?\n- **Spec** — does the code faithfully implement the originating issue or spec?\n\nRun the two axes **independently**, in separate workers where the harness allows, so neither\npollutes the other's context. Then aggregate.\n\n## Process\n\n### 1. Pin the fixed point\n\nWhatever the user said is the fixed point — a commit SHA, branch name, tag, `main`, `HEAD~5`.\nIf they did not specify one, ask.\n\nCapture the diff once: `git diff \u003Cfixed-point>...HEAD` (three-dot, so the comparison is\nagainst the merge-base), plus `git log \u003Cfixed-point>..HEAD --oneline`.\n\nConfirm the fixed point resolves (`git rev-parse \u003Cfixed-point>`) and the diff is non-empty\n**before** going further. A bad ref or empty diff must fail here, not inside two workers.\n\n### 2. Identify the spec source\n\nIn order: issue references in the commit messages (`#123`, `Closes #45`); a path the user\npassed as an argument; a spec file under `docs\u002F`, `specs\u002F`, or the repo's scratch area\nmatching the branch or feature. Use `to-issues` to resolve a hosted reference, and only when\na tracker is configured and authorized.\n\nIf nothing is found, ask. If the user says there is no spec, the Spec axis reports\n\"no spec available\" rather than inventing one.\n\n### 3. Identify the standards sources\n\nAnything documenting how code should be written here — `CODING_STANDARDS.md`,\n`CONTRIBUTING.md`, `AGENTS.md`, `CONTEXT.md`.\n\nOn top of that, the Standards axis always carries the **smell baseline** in\n[SMELL-BASELINE.md](SMELL-BASELINE.md), which applies even when a repo documents nothing.\nTwo rules bind it: **the repo overrides** (a documented standard always wins, and where it\nendorses something the baseline would flag, suppress the smell), and **every smell is a\njudgement call** — a labelled heuristic, never a hard violation. Skip anything tooling\nalready enforces.\n\n### 4. Run both axes\n\n**Standards brief** — give it the diff command, the commit list, the standards sources\nfound, and the smell baseline **pasted in full** (the worker has no other access to it).\nAsk for: every place the diff violates a documented standard, citing the file and rule; and\nany baseline smell, named with the hunk quoted. Distinguish hard violations from judgement\ncalls — documented breaches can be hard, baseline smells never are. Under 400 words.\n\n**Spec brief** — give it the diff command, the commit list, and the spec. Ask for:\nrequirements the spec asked for that are missing or partial; behaviour in the diff nobody\nasked for (scope creep); and requirements that look implemented but implemented wrongly.\nQuote the spec line for each finding. Under 400 words.\n\nIf there is no spec, skip the Spec axis and say so in the report.\n\n### 5. Aggregate\n\nPresent both reports under `## Standards` and `## Spec`, verbatim or lightly cleaned. Do\n**not** merge or rerank findings across axes.\n\nEnd with one line: total findings per axis, and the worst issue *within each axis*. Do not\npick a single winner across axes — that is exactly the reranking the separation prevents.\n\n## Why two axes\n\nA change can pass one and fail the other:\n\n- Follows every standard but implements the wrong thing → **Standards pass, Spec fail.**\n- Does exactly what the issue asked but breaks the project's conventions → **Spec pass,\n  Standards fail.**\n\nReporting them separately stops one axis from masking the other.\n\nEnd by declaring knowledge kind `review`, then reading\n[ai-catapult-init\u002Fmodules\u002Fknowledge-publish.md](..\u002Fai-catapult-init\u002Fmodules\u002Fknowledge-publish.md) and running its host-neutral producer step — publish when a registry exists, otherwise record `unpublished: \u003Creason>`; never fail the skill because of the registry.\n",{"name":5,"description":7},"main","037fe34299eb9c4a30b51f1a6bd101eae1c469b1","04-validate-handoff\u002Fcode-review","https:\u002F\u002Fgithub.com\u002Fr3dlex\u002Fskills","https:\u002F\u002Fgithub.com\u002Fr3dlex","2026-10-29 16:22:54",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add r3dlex\u002Fskills --skill code-review",{"tool":59,"command":60},"bunx","bunx skills add r3dlex\u002Fskills --skill code-review",{"tool":62,"command":63},"pnpm","pnpm dlx skills add r3dlex\u002Fskills --skill code-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fr3dlex\u002Fskills\u002Fblob\u002Fmain\u002F04-validate-handoff\u002Fcode-review\u002FSKILL.md",true,[67],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"SMELL-BASELINE.md","REFERENCE","参考文档",2408,"https:\u002F\u002Fgithub.com\u002Fr3dlex\u002Fskills\u002Fblob\u002Fmain\u002F04-validate-handoff\u002Fcode-review\u002FSMELL-BASELINE.md",[74,82,93,102,112,134],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":42},"01M6R652E42RZT7M2V3RWW991Z","skill","Fixture.","https:\u002F\u002Fgithub.com\u002Fr3dlex\u002Fskills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fcatalog-malformed\u002Fskill\u002FSKILL.md",[],[81],"fixture",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":91,"publishedAt":42},"01M6R64MTPF0FGWHFS4DWP40GR","stable-skill","Fixture stable-skill.","https:\u002F\u002Fgithub.com\u002Fr3dlex\u002Fskills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fcatalog-lifecycle\u002Fstable-skill\u002FSKILL.md",[88],{"categoryNo":89,"categoryName":90,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[92,81],"stable skill",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":100,"publishedAt":42},"01M6R64HD4QVAYM2R0JSYNVDJW","experimental-skill","Fixture experimental-skill.","https:\u002F\u002Fgithub.com\u002Fr3dlex\u002Fskills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fcatalog-lifecycle\u002Fexperimental-skill\u002FSKILL.md",[99],{"categoryNo":89,"categoryName":90,"taxonomyType":20,"taxonomyTypeDesc":21},[101,81],"experimental skill",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":109,"publishedAt":42},"01M6R64FZH05TEJQW75QX1E5XD","deprecated-skill","Fixture deprecated-skill.","https:\u002F\u002Fgithub.com\u002Fr3dlex\u002Fskills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fcatalog-lifecycle\u002Fdeprecated-skill\u002FSKILL.md",[108],{"categoryNo":89,"categoryName":90,"taxonomyType":20,"taxonomyTypeDesc":21},[110,111,81],"deprecated skill","deprecated",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":42},"01M6R64D13X5DC980GREWFSSFQ","karpathy-guidelines","Apply think-before-coding, simplicity, surgical-change, and goal-driven engineering rules. Use when planning, implementing, or reviewing code.","https:\u002F\u002Fgithub.com\u002Fr3dlex\u002Fskills\u002Fblob\u002Fmain\u002Freference\u002Fgolden-skills\u002F.agents\u002Fskills\u002Fkarpathy-guidelines\u002FSKILL.md",[],[119,120,121,122,36,123,124,125,126,127,128,129,41,130,131,30,132,133],"karpathy guidelines","karpathy","guidelines","Rules","simplicity","goal","think","driven","reviewing code","implementing","apply","coding","change","planning","engineering",{"skillNo":135,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":42},"01M6R640ZS60BRV9P49FT46ZJX","https:\u002F\u002Fgithub.com\u002Fr3dlex\u002Fskills\u002Fblob\u002Fmain\u002Freference\u002Fgolden-root\u002F.agents\u002Fskills\u002Fkarpathy-guidelines\u002FSKILL.md",[],[121,119,120,131,126,30,132,133,130,122,36,123,124,125,127,128,129,41]]