[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77WCNXC28WYFFNS3MPMHWDB":3,"skill-same:01M77WCNXC28WYFFNS3MPMHWDB":47},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M77WCNXC28WYFFNS3MPMHWDB","code-review",null,"Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue\u002Fspec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".","vana-com\u002Fvana-cli","vana-com","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F123112561?v=4","01M77WCAG7S42PDY7VTEVWXQD1","Vana","01M77WCAGV436KWGZWHNHZXGVH",2,"MIT","https:\u002F\u002Fgithub.com\u002Fvana-com\u002Fvana-cli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcode-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: code-review\ndescription: 'Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo''s documented coding standards?) and Spec (does the code match what the originating issue\u002Fspec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".'\n---\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 \u002F spec?\n\nBoth axes run as **parallel sub-agents** so they don't pollute each other's context, then this skill aggregates their findings.\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, `origin\u002Fmain`, `HEAD~5`, etc.). If they didn't specify one, default to `origin\u002Fmain` for a feature branch and say so; for an open PR use its real base (`gh pr view --json baseRefName`).\n\nCapture the diff command once: `git diff \u003Cfixed-point>...HEAD` (three-dot, so the comparison is against the merge-base). Also note the list of commits via `git log \u003Cfixed-point>..HEAD --oneline`.\n\nBefore going further, confirm the fixed point resolves (`git rev-parse \u003Cfixed-point>`) and the diff is non-empty. A bad ref or empty diff should fail here, not inside two parallel sub-agents.\n\n### 2. Identify the spec source\n\nLook for the originating spec, in this order:\n\n1. Issue or ticket references in the branch name, commit messages, or PR body (`#123`, `Closes #45`, Linear keys such as `BUI-123` or `PRO-123`). Fetch GitHub issues and PRs with `gh issue view \u003Cn>` \u002F `gh pr view \u003Cn> --json title,body`. For Linear keys, use the Linear integration if available; otherwise ask the user to paste the ticket.\n2. A path the user passed as an argument.\n3. A spec or design doc under `docs\u002F`, `specs\u002F`, or `.scratch\u002F` matching the branch name or feature.\n4. If nothing is found, ask the user where the spec is. If they say there isn't one, the **Spec** sub-agent will skip and report \"no spec available\".\n\n### 3. Identify the standards sources\n\nAnything in the repo that documents how code should be written. In this repo start with `AGENTS.md` (root, mirrored by `CLAUDE.md`), `CONTRIBUTING.md`, `eslint.config.js`, `.prettierrc`, plus any nearer README in the touched area (`cli\u002FREADME.md`, `connect\u002FREADME.md`).\n\nOn top of whatever the repo documents, the Standards axis always carries the **smell baseline** below: a fixed set of Fowler code smells (_Refactoring_, ch.3) that applies even when a repo documents nothing. Two rules bind it:\n\n- **The repo overrides.** A documented repo standard always wins; where it endorses something the baseline would flag, suppress the smell.\n- **Always a judgement call.** Each smell is a labelled heuristic (\"possible Feature Envy\"), never a hard violation. Like any standard here, skip anything tooling already enforces (ESLint, Prettier, `tsc`).\n\nEach smell reads _what it is_ -> _how to fix_; match it against the diff:\n\n- **Mysterious Name**: a function, variable, or type whose name doesn't reveal what it does or holds. -> rename it; if no honest name comes, the design's murky.\n- **Duplicated Code**: the same logic shape appears in more than one hunk or file in the change. -> extract the shared shape, call it from both.\n- **Feature Envy**: a method that reaches into another object's data more than its own. -> move the method onto the data it envies.\n- **Data Clumps**: the same few fields or params keep travelling together (a type wanting to be born). -> bundle them into one type, pass that.\n- **Primitive Obsession**: a primitive or string standing in for a domain concept that deserves its own type. -> give the concept its own small type.\n- **Repeated Switches**: the same `switch`\u002F`if`-cascade on the same type recurs across the change. -> replace with polymorphism, or one map both sites share.\n- **Shotgun Surgery**: one logical change forces scattered edits across many files in the diff. -> gather what changes together into one module.\n- **Divergent Change**: one file or module is edited for several unrelated reasons. -> split so each module changes for one reason.\n- **Speculative Generality**: abstraction, parameters, or hooks added for needs the spec doesn't have. -> delete it; inline back until a real need shows.\n- **Message Chains**: long `a.b().c().d()` navigation the caller shouldn't depend on. -> hide the walk behind one method on the first object.\n- **Middle Man**: a class or function that mostly just delegates onward. -> cut it, call the real target direct.\n- **Refused Bequest**: a subclass or implementer that ignores or overrides most of what it inherits. -> drop the inheritance, use composition.\n\n### 4. Spawn both sub-agents in parallel\n\n**Standards sub-agent prompt** should include:\n\n- The full diff command and commit list.\n- The list of standards-source files you found in step 3, **plus the smell baseline from step 3** pasted in full (the sub-agent has no other access to it).\n- The brief: \"Report, per file\u002Fhunk where relevant, (a) every place the diff violates a documented standard: cite the standard (file + the rule); and (b) any baseline smell you spot: name it and quote the hunk. Distinguish hard violations from judgement calls: documented-standard breaches can be hard, but baseline smells are always judgement calls, and a documented repo standard overrides the baseline. Skip anything tooling enforces. Under 400 words.\"\n\n**Spec sub-agent prompt** should include:\n\n- The diff command and commit list.\n- The path or fetched contents of the spec.\n- The brief: \"Report: (a) requirements the spec asked for that are missing or partial; (b) behaviour in the diff that wasn't asked for (scope creep); (c) requirements that look implemented but where the implementation looks wrong. Quote the spec line for each finding. Under 400 words.\"\n\nIf the spec is missing, skip the Spec sub-agent and note this in the final report.\n\n### 5. Aggregate\n\nPresent the two reports under `## Standards` and `## Spec` headings, verbatim or lightly cleaned. Do **not** merge or rerank findings, because the two axes are deliberately separate (see _Why two axes_).\n\nEnd with a one-line summary: total findings per axis, and the worst issue _within each axis_ (if any). Don't pick a single winner across axes: that's the reranking the separation exists to prevent.\n\n## Why two axes\n\nA change can pass one axis and fail the other:\n\n- Code that follows every standard but implements the wrong thing -> **Standards pass, Spec fail.**\n- Code that does exactly what the issue asked but breaks the project's conventions -> **Spec pass, Standards fail.**\n\nReporting them separately stops one axis from masking the other.\n","Two-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 \u002F spec?\n\nBoth axes run as **parallel sub-agents** so they don't pollute each other's context, then this skill aggregates their findings.\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, `origin\u002Fmain`, `HEAD~5`, etc.). If they didn't specify one, default to `origin\u002Fmain` for a feature branch and say so; for an open PR use its real base (`gh pr view --json baseRefName`).\n\nCapture the diff command once: `git diff \u003Cfixed-point>...HEAD` (three-dot, so the comparison is against the merge-base). Also note the list of commits via `git log \u003Cfixed-point>..HEAD --oneline`.\n\nBefore going further, confirm the fixed point resolves (`git rev-parse \u003Cfixed-point>`) and the diff is non-empty. A bad ref or empty diff should fail here, not inside two parallel sub-agents.\n\n### 2. Identify the spec source\n\nLook for the originating spec, in this order:\n\n1. Issue or ticket references in the branch name, commit messages, or PR body (`#123`, `Closes #45`, Linear keys such as `BUI-123` or `PRO-123`). Fetch GitHub issues and PRs with `gh issue view \u003Cn>` \u002F `gh pr view \u003Cn> --json title,body`. For Linear keys, use the Linear integration if available; otherwise ask the user to paste the ticket.\n2. A path the user passed as an argument.\n3. A spec or design doc under `docs\u002F`, `specs\u002F`, or `.scratch\u002F` matching the branch name or feature.\n4. If nothing is found, ask the user where the spec is. If they say there isn't one, the **Spec** sub-agent will skip and report \"no spec available\".\n\n### 3. Identify the standards sources\n\nAnything in the repo that documents how code should be written. In this repo start with `AGENTS.md` (root, mirrored by `CLAUDE.md`), `CONTRIBUTING.md`, `eslint.config.js`, `.prettierrc`, plus any nearer README in the touched area (`cli\u002FREADME.md`, `connect\u002FREADME.md`).\n\nOn top of whatever the repo documents, the Standards axis always carries the **smell baseline** below: a fixed set of Fowler code smells (_Refactoring_, ch.3) that applies even when a repo documents nothing. Two rules bind it:\n\n- **The repo overrides.** A documented repo standard always wins; where it endorses something the baseline would flag, suppress the smell.\n- **Always a judgement call.** Each smell is a labelled heuristic (\"possible Feature Envy\"), never a hard violation. Like any standard here, skip anything tooling already enforces (ESLint, Prettier, `tsc`).\n\nEach smell reads _what it is_ -> _how to fix_; match it against the diff:\n\n- **Mysterious Name**: a function, variable, or type whose name doesn't reveal what it does or holds. -> rename it; if no honest name comes, the design's murky.\n- **Duplicated Code**: the same logic shape appears in more than one hunk or file in the change. -> extract the shared shape, call it from both.\n- **Feature Envy**: a method that reaches into another object's data more than its own. -> move the method onto the data it envies.\n- **Data Clumps**: the same few fields or params keep travelling together (a type wanting to be born). -> bundle them into one type, pass that.\n- **Primitive Obsession**: a primitive or string standing in for a domain concept that deserves its own type. -> give the concept its own small type.\n- **Repeated Switches**: the same `switch`\u002F`if`-cascade on the same type recurs across the change. -> replace with polymorphism, or one map both sites share.\n- **Shotgun Surgery**: one logical change forces scattered edits across many files in the diff. -> gather what changes together into one module.\n- **Divergent Change**: one file or module is edited for several unrelated reasons. -> split so each module changes for one reason.\n- **Speculative Generality**: abstraction, parameters, or hooks added for needs the spec doesn't have. -> delete it; inline back until a real need shows.\n- **Message Chains**: long `a.b().c().d()` navigation the caller shouldn't depend on. -> hide the walk behind one method on the first object.\n- **Middle Man**: a class or function that mostly just delegates onward. -> cut it, call the real target direct.\n- **Refused Bequest**: a subclass or implementer that ignores or overrides most of what it inherits. -> drop the inheritance, use composition.\n\n### 4. Spawn both sub-agents in parallel\n\n**Standards sub-agent prompt** should include:\n\n- The full diff command and commit list.\n- The list of standards-source files you found in step 3, **plus the smell baseline from step 3** pasted in full (the sub-agent has no other access to it).\n- The brief: \"Report, per file\u002Fhunk where relevant, (a) every place the diff violates a documented standard: cite the standard (file + the rule); and (b) any baseline smell you spot: name it and quote the hunk. Distinguish hard violations from judgement calls: documented-standard breaches can be hard, but baseline smells are always judgement calls, and a documented repo standard overrides the baseline. Skip anything tooling enforces. Under 400 words.\"\n\n**Spec sub-agent prompt** should include:\n\n- The diff command and commit list.\n- The path or fetched contents of the spec.\n- The brief: \"Report: (a) requirements the spec asked for that are missing or partial; (b) behaviour in the diff that wasn't asked for (scope creep); (c) requirements that look implemented but where the implementation looks wrong. Quote the spec line for each finding. Under 400 words.\"\n\nIf the spec is missing, skip the Spec sub-agent and note this in the final report.\n\n### 5. Aggregate\n\nPresent the two reports under `## Standards` and `## Spec` headings, verbatim or lightly cleaned. Do **not** merge or rerank findings, because the two axes are deliberately separate (see _Why two axes_).\n\nEnd with a one-line summary: total findings per axis, and the worst issue _within each axis_ (if any). Don't pick a single winner across axes: that's the reranking the separation exists to prevent.\n\n## Why two axes\n\nA change can pass one axis and fail the other:\n\n- Code that follows every standard but implements the wrong thing -> **Standards pass, Spec fail.**\n- Code that does exactly what the issue asked but breaks the project's conventions -> **Spec pass, Standards fail.**\n\nReporting them separately stops one axis from masking the other.\n",{"name":5,"description":7},"main","a55d0a0006da6a743b6452796435afa6ed177dd8",".agents\u002Fskills\u002Fcode-review",0,"https:\u002F\u002Fgithub.com\u002Fvana-com\u002Fvana-cli","https:\u002F\u002Fgithub.com\u002Fvana-com","https:\u002F\u002Fvana.org","The first open protocol for data sovereignty.","2026-11-13 18:19:18",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add vana-com\u002Fvana-cli --skill code-review",{"tool":39,"command":40},"bunx","bunx skills add vana-com\u002Fvana-cli --skill code-review",{"tool":42,"command":43},"pnpm","pnpm dlx skills add vana-com\u002Fvana-cli --skill code-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvana-com\u002Fvana-cli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcode-review\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7BD5YJ16KD0X3M379XA2A4A","verify-setup-resume","Verify BUI-936 setup\u002Fresume identities, funding readiness and overlapping resumes. Use when changing app request, test-credit transport or the request journal. Runs bounded TLA+ checks and offline real-code replays without live funding or paid reads.","https:\u002F\u002Fgithub.com\u002Fvana-com\u002Fvana-cli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-setup-resume\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7BD5V2155AM7W1PWRBY237Y","verify-server-supervision","Verify the local Personal Server stop and restart boundary. Use when changing the supervisor's backoff, port probing, replacement launch or Stop handling.","https:\u002F\u002Fgithub.com\u002Fvana-com\u002Fvana-cli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-server-supervision\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7BD5PPVKFVVGS9B846B99ES","verify-paid-read-recovery","Verify interrupted and overlapping CLI paid reads, receipt-file writers and dead-owner recovery. Use when changing src\u002Fcli\u002Fapp\u002Fread.ts, src\u002Fcore\u002Freceipts.ts or src\u002Fcore\u002Freceipts-lock.ts. Runs TLA+ models and offline real-code replays without live paid reads.","https:\u002F\u002Fgithub.com\u002Fvana-com\u002Fvana-cli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-paid-read-recovery\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7BD5JDEGV165NFZJWSWJBN4","verify-mainnet-registration","Verify mainnet app registration and Account association recovery. Use for the registration journal, gateway confirmation, retry, or ownership check.","https:\u002F\u002Fgithub.com\u002Fvana-com\u002Fvana-cli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-mainnet-registration\u002FSKILL.md",[],[],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7BD5ETK33JAD1F1XQXGPYYG","verify-hosted-provisioning","Verify hosted Personal Server resource ownership across create and delete. Use for Connect's server API, provisioning-row updates, or deprovisioning admission.","https:\u002F\u002Fgithub.com\u002Fvana-com\u002Fvana-cli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-hosted-provisioning\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7BD5BBKFHJ86JFBE8KT1S78","verify-export-settlement","Verify queued export owner binding and generation settlement. Use for result publication, pending upload receipts, or retry and sync changes.","https:\u002F\u002Fgithub.com\u002Fvana-com\u002Fvana-cli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-export-settlement\u002FSKILL.md",[],[]]