[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M735EW787CDYKAH0N32ZR4CD":3,"skill-same:01M735EW787CDYKAH0N32ZR4CD":52},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M735EW787CDYKAH0N32ZR4CD","code-review",null,"Review the diff since a fixed point on two axes, Standards (the AGENTS.md ladder, ADRs, design notes) and Spec (the originating GitHub issue). Use to review a branch, a PR, or work in progress.","wso2\u002Flabs-agentic-engineer","wso2","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F533043?v=4","01M6CDAFS40T9Y86DYXWE0NJES","WSO2","01M735EE4N2PP2ZR56AX7DNPNP",24,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fwso2\u002Flabs-agentic-engineer\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcode-review\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: code-review\ndescription: Review the diff since a fixed point on two axes, Standards (the AGENTS.md ladder, ADRs, design notes) and Spec (the originating GitHub issue). Use to review a branch, a PR, or work in progress.\n---\n\nTwo parallel sub-agents review `git diff \u003Cfixed-point>...HEAD`, one per axis, so neither pollutes the other's context. This skill pins the inputs, dispatches both, and reports them side by side. Fit and comment debt are separate manual skills: `\u002Ffit-review`, `\u002Fcomment-debt`.\n\n## 1. Pin the fixed point\n\nThe user's ref if given, else `main`. Confirm `git rev-parse \u003Cref>` resolves and the three-dot diff is non-empty before dispatching anything. Keep the diff command and `git log \u003Cref>..HEAD --oneline` for every prompt.\n\n## 2. Find the spec\n\nIn order: an issue number in the branch name, commit messages, or open PR body (`gh pr view --json body`), fetched with `gh issue view \u003Cn> --comments`; a path the user passed; a plan under `docs\u002Fdesign\u002Fdraft\u002F` matching the branch. Nothing found: ask once, and if there is no spec the Spec axis reports \"no spec available\" and is skipped.\n\n## 3. Find the standards\n\nFor each changed file, the nearest `AGENTS.md` up the tree plus the root one, and any ADR in `docs\u002Fdecisions\u002F` or `design\u002F` note the change touches. On top of those, the smell baseline below. Two rules bind the axis:\n\n- **The repo overrides.** A documented standard wins; where it endorses something the baseline flags, suppress the smell.\n- **Tooling is out of scope.** Anything `make lint`, `make typecheck`, `make deadcode-ts-check`, or `make license-check` would catch is not a finding.\n\n## 4. Dispatch the two sub-agents\n\n**Standards prompt:** the diff command, commit list, the standards files from step 3, the smell baseline pasted in full, and the brief: \"Read every standards file. Report, per file or hunk, (a) every place the diff breaks a documented standard, citing file and rule; (b) every baseline smell, named, with the hunk quoted. Documented breaches may be hard violations; smells are always judgement calls. Under 400 words.\"\n\n**Spec prompt:** the diff command, commit list, the fetched spec, and the brief: \"Report (a) requirements missing or partial; (b) behaviour the spec did not ask for; (c) requirements that look implemented but wrong. Quote the spec line for each finding. Under 400 words.\"\n\n## 5. Report\n\nPrint both under `## Standards` and `## Spec`, verbatim or lightly cleaned, then one line per axis: finding count and the worst issue. The axes stay separate because a change can pass any of them while failing another; never merge or rerank across them.\n\n## Smell baseline\n\nFowler's code smells (_Refactoring_, ch. 3), applied on top of the documented standards. Each line reads *what it is* → *how to fix*.\n\n- **Mysterious Name**: a name that does not reveal what the thing does or holds. → rename; if no honest name comes, the design is murky.\n- **Duplicated Code**: the same logic shape in more than one hunk or file of the change. → extract the shared shape.\n- **Feature Envy**: a function reaching into another type's data more than its own. → move it onto the data it envies.\n- **Data Clumps**: the same few fields or params travelling together. → bundle them into one type.\n- **Primitive Obsession**: a primitive or string standing in for a domain concept. → give the concept its own small type.\n- **Repeated Switches**: the same `switch` or `if` cascade on the same type recurring across the change. → one map or polymorphism both sites share.\n- **Shotgun Surgery**: one logical change forcing scattered edits across many files. → gather what changes together into one module.\n- **Divergent Change**: one file edited for several unrelated reasons. → split so each module changes for one reason.\n- **Speculative Generality**: abstraction, params, or hooks for needs the spec does not have. → delete; inline until a real need shows.\n- **Message Chains**: long `a.b().c().d()` navigation the caller should not depend on. → hide the walk behind one method on the first object.\n- **Middle Man**: a type or function that mostly delegates onward. → cut it, call the real target.\n","Two parallel sub-agents review `git diff \u003Cfixed-point>...HEAD`, one per axis, so neither pollutes the other's context. This skill pins the inputs, dispatches both, and reports them side by side. Fit and comment debt are separate manual skills: `\u002Ffit-review`, `\u002Fcomment-debt`.\n\n## 1. Pin the fixed point\n\nThe user's ref if given, else `main`. Confirm `git rev-parse \u003Cref>` resolves and the three-dot diff is non-empty before dispatching anything. Keep the diff command and `git log \u003Cref>..HEAD --oneline` for every prompt.\n\n## 2. Find the spec\n\nIn order: an issue number in the branch name, commit messages, or open PR body (`gh pr view --json body`), fetched with `gh issue view \u003Cn> --comments`; a path the user passed; a plan under `docs\u002Fdesign\u002Fdraft\u002F` matching the branch. Nothing found: ask once, and if there is no spec the Spec axis reports \"no spec available\" and is skipped.\n\n## 3. Find the standards\n\nFor each changed file, the nearest `AGENTS.md` up the tree plus the root one, and any ADR in `docs\u002Fdecisions\u002F` or `design\u002F` note the change touches. On top of those, the smell baseline below. Two rules bind the axis:\n\n- **The repo overrides.** A documented standard wins; where it endorses something the baseline flags, suppress the smell.\n- **Tooling is out of scope.** Anything `make lint`, `make typecheck`, `make deadcode-ts-check`, or `make license-check` would catch is not a finding.\n\n## 4. Dispatch the two sub-agents\n\n**Standards prompt:** the diff command, commit list, the standards files from step 3, the smell baseline pasted in full, and the brief: \"Read every standards file. Report, per file or hunk, (a) every place the diff breaks a documented standard, citing file and rule; (b) every baseline smell, named, with the hunk quoted. Documented breaches may be hard violations; smells are always judgement calls. Under 400 words.\"\n\n**Spec prompt:** the diff command, commit list, the fetched spec, and the brief: \"Report (a) requirements missing or partial; (b) behaviour the spec did not ask for; (c) requirements that look implemented but wrong. Quote the spec line for each finding. Under 400 words.\"\n\n## 5. Report\n\nPrint both under `## Standards` and `## Spec`, verbatim or lightly cleaned, then one line per axis: finding count and the worst issue. The axes stay separate because a change can pass any of them while failing another; never merge or rerank across them.\n\n## Smell baseline\n\nFowler's code smells (_Refactoring_, ch. 3), applied on top of the documented standards. Each line reads *what it is* → *how to fix*.\n\n- **Mysterious Name**: a name that does not reveal what the thing does or holds. → rename; if no honest name comes, the design is murky.\n- **Duplicated Code**: the same logic shape in more than one hunk or file of the change. → extract the shared shape.\n- **Feature Envy**: a function reaching into another type's data more than its own. → move it onto the data it envies.\n- **Data Clumps**: the same few fields or params travelling together. → bundle them into one type.\n- **Primitive Obsession**: a primitive or string standing in for a domain concept. → give the concept its own small type.\n- **Repeated Switches**: the same `switch` or `if` cascade on the same type recurring across the change. → one map or polymorphism both sites share.\n- **Shotgun Surgery**: one logical change forcing scattered edits across many files. → gather what changes together into one module.\n- **Divergent Change**: one file edited for several unrelated reasons. → split so each module changes for one reason.\n- **Speculative Generality**: abstraction, params, or hooks for needs the spec does not have. → delete; inline until a real need shows.\n- **Message Chains**: long `a.b().c().d()` navigation the caller should not depend on. → hide the walk behind one method on the first object.\n- **Middle Man**: a type or function that mostly delegates onward. → cut it, call the real target.\n",{"name":5,"description":7},"main","e3b5fc8668f26761380b2d4965719f2d8f2eb246",".agents\u002Fskills\u002Fcode-review","https:\u002F\u002Fgithub.com\u002Fwso2\u002Flabs-agentic-engineer","https:\u002F\u002Fgithub.com\u002Fwso2","https:\u002F\u002Fwso2.com","Welcome to the WSO2 source code! For info on working with the WSO2 repositories and contributing code, click the link below.","2026-11-11 15:36:27",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add wso2\u002Flabs-agentic-engineer --skill code-review",{"tool":38,"command":39},"bunx","bunx skills add wso2\u002Flabs-agentic-engineer --skill code-review",{"tool":41,"command":42},"pnpm","pnpm dlx skills add wso2\u002Flabs-agentic-engineer --skill code-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwso2\u002Flabs-agentic-engineer\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcode-review\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",100,"https:\u002F\u002Fgithub.com\u002Fwso2\u002Flabs-agentic-engineer\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcode-review\u002Fagents\u002Fopenai.yaml",[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M735MP9NFFRPS260G9D16JQX","validation-task","Load when working a VALIDATION task dispatched by WSO2 Labs Agentic Engineer — judging a deployed version against its acceptance criteria.","https:\u002F\u002Fgithub.com\u002Fwso2\u002Flabs-agentic-engineer\u002Fblob\u002Fmain\u002Fskills\u002Fvalidation-task\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M735MJ8ZMRZR20A57TMF7R9Q","thunder-authentication","Apply when a component sits on the project's sign-in — a SPA whose users authenticate through the auth platform-resource dependency, or a protected backend those signed-in users call.","https:\u002F\u002Fgithub.com\u002Fwso2\u002Flabs-agentic-engineer\u002Fblob\u002Fmain\u002Fskills\u002Fthunder-authentication\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M735MFQMY8DY1EM7JKS784D3","task-planning","Use when planning a version's build from a design — the plan turn that writes the build's checklist with planBuild, one item per feature the version carries in build order, after a Foundation item when the version needs one.","https:\u002F\u002Fgithub.com\u002Fwso2\u002Flabs-agentic-engineer\u002Fblob\u002Fmain\u002Fskills\u002Ftask-planning\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M735MCJQ4EVH7G4ZFMC682Y4","start","Use when kicking off a project from its idea — the product pass that agrees the feature list and writes the product page, the product-wide page and a stub per feature — or re-running \u002Fstart on a project that already has requirements.","https:\u002F\u002Fgithub.com\u002Fwso2\u002Flabs-agentic-engineer\u002Fblob\u002Fmain\u002Fskills\u002Fstart\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M735M9R050KT3H34PVXN2MKK","security-design","Write specs\u002Fdesign\u002Fsecurity.json when a design has sign-in, permissions, roles or test users — the permission catalog every API operation is gated on.","https:\u002F\u002Fgithub.com\u002Fwso2\u002Flabs-agentic-engineer\u002Fblob\u002Fmain\u002Fskills\u002Fsecurity-design\u002FSKILL.md",[],[],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M735M60CTW4S7XMS6XCX9A7Y","resolve-dependency","Use for taking one external dependency from open to resolved — `\u002Fresolve-dependency \u003Cname> [answer]` names it and may carry the provider the user chose; `\u002Fresolve-dependencies` walks every open one in turn. Ask which provider (their suggestions as options; never choose for them), get its interface on disk (found, uploaded from the card, or assumed under the authorization the card records), then derive the config keys.","https:\u002F\u002Fgithub.com\u002Fwso2\u002Flabs-agentic-engineer\u002Fblob\u002Fmain\u002Fskills\u002Fresolve-dependency\u002FSKILL.md",[],[]]