[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D32PM2BYJEAWKBJ433ZE9S":3,"skill-same:01M7D32PM2BYJEAWKBJ433ZE9S":46},{"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":6,"updatedAt":31,"install":32,"resources":45},"01M7D32PM2BYJEAWKBJ433ZE9S","code-review",null,"Run a comprehensive code review","Pibomeister\u002Fagent-kit","Pibomeister","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11633791?v=4","01M7D2NBHEKARMHN9MPV2J80XD","Eduardo Picazo","01M7D2NBJ3Z33SGSYCZ0KBD5DE",0,"MIT","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Fprovenance\u002Fdonor-snapshots\u002Fomx@cb955b0d5bec\u002Fskills\u002Fcode-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: code-review\ndescription: Run a comprehensive code review\n---\n\n# Code Review Task Card\n\nUse this explicit opt-in for a merge-readiness review. Shared operating invariants\nlive in `templates\u002FAGENTS.md`; this card only defines review-specific behavior.\n\n## When to use\n\n- The user asks for a code review or quality\u002Fsecurity assessment.\n- A change is ready for review before merge, or a major feature needs an independent review.\n- Do not activate this card for implementation, broad planning, or automatic cleanup.\n\n## Inputs\n\n- Scope: the requested files, commit, PR, or whole diff.\n- Requirements\u002Fspecification, acceptance criteria, and relevant test\u002FCI evidence.\n- Existing review artifacts and known risks, if any.\n- If the user says `continue`, advance the current verified review step rather than restarting discovery.\n\nStart by recording the scope:\n\n```sh\ngit status --short\ngit diff --stat\ngit diff -- \u003Cscope>\n```\n\n## Execution\n\n1. Identify changed files and review boundaries; do not silently widen the scope.\n2. Launch the `code-reviewer` and `architect` agents in parallel. Both lanes run in parallel on a clean context with explicit scope and artifacts. If either lane cannot be launched or does not return evidence, report `independent review unavailable`; do **not** substitute the current\u002Fauthoring lane, and do **not** approve or mark the review merge-ready.\n3. Respect the user's current model and reasoning\u002Feffort selection. Do not pass `model` or `reasoning_effort` overrides in review-lane calls.\n\n```text\ntask(\n  agent_type=\"code-reviewer\",\n  prompt=\"CODE REVIEW TASK\n\nReview the supplied scope for spec compliance, security, quality, performance, and maintainability.\nReturn files reviewed, severity-rated findings with file:line evidence and concrete fixes,\nand a recommendation: APPROVE \u002F REQUEST CHANGES \u002F COMMENT. Do not review architecture.\nScope: [scope and artifacts]\"\n)\n\ntask(\n  agent_type=\"architect\",\n  prompt=\"ARCHITECTURE \u002F DEVIL'S-ADVOCATE REVIEW TASK\n\nReview the same scope for boundaries, interfaces, hidden coupling, long-term tradeoffs,\nand the strongest counterargument against approval. Return file:line evidence,\nrecommendations, and Architectural Status: CLEAR \u002F WATCH \u002F BLOCK.\nScope: [scope and artifacts]\"\n)\n```\n\n## Review taxonomy\n\n- `code-reviewer` checks **Security**, **Code Quality**, **Performance**, **Best Practices**, and **Maintainability**.\n- Rate each finding: **CRITICAL** (security or data-loss blocker), **HIGH** (bug\u002Fmajor smell), **MEDIUM** (important improvement), or **LOW** (style\u002Fsuggestion).\n- `architect` checks explicit boundaries\u002Finterfaces, hidden coupling, long-horizon tradeoffs, and devil's-advocate concerns. Status is **CLEAR**, **WATCH** (non-blocking concern), or **BLOCK** (merge blocker).\n- Every finding names `file:line`, issue, risk, and a concrete fix; distinguish facts from suggestions.\n\n## State\u002FHUD Phase Contract\n\n- Standalone `$code-review` relies on hook-owned `skill-active-state.json` (`skill:\"code-review\"`, `phase:\"planning\"`); do not create `code-review-state.json`.\n- Inside Autopilot, keep `mode:\"autopilot\"` active with `current_phase:\"code-review\"` \u002F skill-active `phase:\"code-review\"`; do not activate a peer workflow.\n- On clean review, persist the artifact under Autopilot `handoff_artifacts.code_review` before moving to `ultraqa`. On non-clean review, persist findings and use `rework` or `ralplan` as appropriate.\n\n```sh\nomx state write --input '{\"mode\":\"autopilot\",\"active\":true,\"current_phase\":\"code-review\"}' --json\n```\n\n## Final Synthesis and gate\n\n### Architectural Status Contract\n\nCombine the `code-reviewer` recommendation and architect status. Approval requires explicit evidence from both independent lanes; missing or failed delegation is a blocking unavailable-review state, not an approval fallback. The final report must make architect blockers impossible to miss.\n\n- If architect status is **BLOCK**, final recommendation is **REQUEST CHANGES**.\n- Else if `code-reviewer` recommendation is **REQUEST CHANGES**, final recommendation is **REQUEST CHANGES**.\n- Else if architect status is **WATCH**, final recommendation is **COMMENT**.\n- Else final recommendation follows the `code-reviewer` lane.\n\nApproval criteria: **APPROVE** only when `code-reviewer` returns APPROVE, architect status is `CLEAR`, and both independent lanes returned evidence. **REQUEST CHANGES** for a blocker, unresolved high\u002Fcritical finding, or unavailable lane. **COMMENT** may record non-blocking findings.\n\nDo not self-review as a fallback. If the `code-reviewer` or `architect` path is missing, unavailable, skipped, or fails, block approval until independent lane evidence exists. On the supported `omx ralph` CLI compatibility path, findings may trigger automatic fix follow-up without another permission prompt; plain `code-review` itself remains read-only and does **not** promise auto-fix.\n\n## Evidence\u002Foutput contract\n\nReturn a concise report containing:\n\n```text\nCODE REVIEW REPORT\nFiles Reviewed: \u003Ccount>\nTotal Issues: 0\nArchitectural Status: CLEAR | WATCH | BLOCK\nCRITICAL (0) | HIGH (0) | MEDIUM (0) | LOW (0)\nFindings: file:line -> issue, risk, concrete fix (or none)\nARCHITECTURE WATCHLIST: concern, status, recommendation (or none)\n- code-reviewer recommendation: COMMENT\n- architect status: WATCH\n- final recommendation: COMMENT\nRECOMMENDATION: COMMENT\n```\n\nReplace the illustrative counts and verdict with observed values. Include scope,\nlane evidence\u002Fartifact references, unresolved risks, and validation gaps.\n\n## Exit condition\n\nStop when the scoped diff has two independent lane results and a deterministic final\nrecommendation. Report `APPROVE` only under the approval criteria; otherwise leave a\nbounded `REQUEST CHANGES`, `COMMENT`, or unavailable-review result. Never claim\nmerge-ready without the required evidence.\n","# Code Review Task Card\n\nUse this explicit opt-in for a merge-readiness review. Shared operating invariants\nlive in `templates\u002FAGENTS.md`; this card only defines review-specific behavior.\n\n## When to use\n\n- The user asks for a code review or quality\u002Fsecurity assessment.\n- A change is ready for review before merge, or a major feature needs an independent review.\n- Do not activate this card for implementation, broad planning, or automatic cleanup.\n\n## Inputs\n\n- Scope: the requested files, commit, PR, or whole diff.\n- Requirements\u002Fspecification, acceptance criteria, and relevant test\u002FCI evidence.\n- Existing review artifacts and known risks, if any.\n- If the user says `continue`, advance the current verified review step rather than restarting discovery.\n\nStart by recording the scope:\n\n```sh\ngit status --short\ngit diff --stat\ngit diff -- \u003Cscope>\n```\n\n## Execution\n\n1. Identify changed files and review boundaries; do not silently widen the scope.\n2. Launch the `code-reviewer` and `architect` agents in parallel. Both lanes run in parallel on a clean context with explicit scope and artifacts. If either lane cannot be launched or does not return evidence, report `independent review unavailable`; do **not** substitute the current\u002Fauthoring lane, and do **not** approve or mark the review merge-ready.\n3. Respect the user's current model and reasoning\u002Feffort selection. Do not pass `model` or `reasoning_effort` overrides in review-lane calls.\n\n```text\ntask(\n  agent_type=\"code-reviewer\",\n  prompt=\"CODE REVIEW TASK\n\nReview the supplied scope for spec compliance, security, quality, performance, and maintainability.\nReturn files reviewed, severity-rated findings with file:line evidence and concrete fixes,\nand a recommendation: APPROVE \u002F REQUEST CHANGES \u002F COMMENT. Do not review architecture.\nScope: [scope and artifacts]\"\n)\n\ntask(\n  agent_type=\"architect\",\n  prompt=\"ARCHITECTURE \u002F DEVIL'S-ADVOCATE REVIEW TASK\n\nReview the same scope for boundaries, interfaces, hidden coupling, long-term tradeoffs,\nand the strongest counterargument against approval. Return file:line evidence,\nrecommendations, and Architectural Status: CLEAR \u002F WATCH \u002F BLOCK.\nScope: [scope and artifacts]\"\n)\n```\n\n## Review taxonomy\n\n- `code-reviewer` checks **Security**, **Code Quality**, **Performance**, **Best Practices**, and **Maintainability**.\n- Rate each finding: **CRITICAL** (security or data-loss blocker), **HIGH** (bug\u002Fmajor smell), **MEDIUM** (important improvement), or **LOW** (style\u002Fsuggestion).\n- `architect` checks explicit boundaries\u002Finterfaces, hidden coupling, long-horizon tradeoffs, and devil's-advocate concerns. Status is **CLEAR**, **WATCH** (non-blocking concern), or **BLOCK** (merge blocker).\n- Every finding names `file:line`, issue, risk, and a concrete fix; distinguish facts from suggestions.\n\n## State\u002FHUD Phase Contract\n\n- Standalone `$code-review` relies on hook-owned `skill-active-state.json` (`skill:\"code-review\"`, `phase:\"planning\"`); do not create `code-review-state.json`.\n- Inside Autopilot, keep `mode:\"autopilot\"` active with `current_phase:\"code-review\"` \u002F skill-active `phase:\"code-review\"`; do not activate a peer workflow.\n- On clean review, persist the artifact under Autopilot `handoff_artifacts.code_review` before moving to `ultraqa`. On non-clean review, persist findings and use `rework` or `ralplan` as appropriate.\n\n```sh\nomx state write --input '{\"mode\":\"autopilot\",\"active\":true,\"current_phase\":\"code-review\"}' --json\n```\n\n## Final Synthesis and gate\n\n### Architectural Status Contract\n\nCombine the `code-reviewer` recommendation and architect status. Approval requires explicit evidence from both independent lanes; missing or failed delegation is a blocking unavailable-review state, not an approval fallback. The final report must make architect blockers impossible to miss.\n\n- If architect status is **BLOCK**, final recommendation is **REQUEST CHANGES**.\n- Else if `code-reviewer` recommendation is **REQUEST CHANGES**, final recommendation is **REQUEST CHANGES**.\n- Else if architect status is **WATCH**, final recommendation is **COMMENT**.\n- Else final recommendation follows the `code-reviewer` lane.\n\nApproval criteria: **APPROVE** only when `code-reviewer` returns APPROVE, architect status is `CLEAR`, and both independent lanes returned evidence. **REQUEST CHANGES** for a blocker, unresolved high\u002Fcritical finding, or unavailable lane. **COMMENT** may record non-blocking findings.\n\nDo not self-review as a fallback. If the `code-reviewer` or `architect` path is missing, unavailable, skipped, or fails, block approval until independent lane evidence exists. On the supported `omx ralph` CLI compatibility path, findings may trigger automatic fix follow-up without another permission prompt; plain `code-review` itself remains read-only and does **not** promise auto-fix.\n\n## Evidence\u002Foutput contract\n\nReturn a concise report containing:\n\n```text\nCODE REVIEW REPORT\nFiles Reviewed: \u003Ccount>\nTotal Issues: 0\nArchitectural Status: CLEAR | WATCH | BLOCK\nCRITICAL (0) | HIGH (0) | MEDIUM (0) | LOW (0)\nFindings: file:line -> issue, risk, concrete fix (or none)\nARCHITECTURE WATCHLIST: concern, status, recommendation (or none)\n- code-reviewer recommendation: COMMENT\n- architect status: WATCH\n- final recommendation: COMMENT\nRECOMMENDATION: COMMENT\n```\n\nReplace the illustrative counts and verdict with observed values. Include scope,\nlane evidence\u002Fartifact references, unresolved risks, and validation gaps.\n\n## Exit condition\n\nStop when the scoped diff has two independent lane results and a deterministic final\nrecommendation. Report `APPROVE` only under the approval criteria; otherwise leave a\nbounded `REQUEST CHANGES`, `COMMENT`, or unavailable-review result. Never claim\nmerge-ready without the required evidence.\n",{"name":5,"description":7},"main","e0232821c4abbcd4338d6018c20fb70f1b74336b","provenance\u002Fdonor-snapshots\u002Fomx@cb955b0d5bec\u002Fskills\u002Fcode-review",3,"https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit","https:\u002F\u002Fgithub.com\u002FPibomeister","www.eduardopicazoenriquez.com","2026-11-15 00:56:58",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Pibomeister\u002Fagent-kit --skill code-review",{"tool":38,"command":39},"bunx","bunx skills add Pibomeister\u002Fagent-kit --skill code-review",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Pibomeister\u002Fagent-kit --skill code-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Fprovenance\u002Fdonor-snapshots\u002Fomx@cb955b0d5bec\u002Fskills\u002Fcode-review\u002FSKILL.md",true,[],[47,54,59,64,69,74],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7D3JZP2026RGY6XX1MC3NQQ","alpha","Human-started command: it runs only when the human's message begins with `\u002Fak:alpha`. On any other request do not load or follow it; tell the human to type that command. Runs the alpha workflow when a human asks for it.","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fvalid\u002Fminimal\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":55,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7D3JA593Q3RBYJXKVZ37Y2K","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid\u002F25-article-tier-outside-vocabulary\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":60,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7D3HQDDAZTAPGWCPGDPNVBQ","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid\u002F24-article-without-triggers\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":65,"name":49,"nameZh":6,"description":50,"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},"01M7D3HK074TK3ZWK1ZZNQVPB0","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid\u002F23-enforced-by-without-predicate\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":70,"name":49,"nameZh":6,"description":50,"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},"01M7D3HGHQM5C5TBSXBCE2WFHW","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid\u002F22-article-without-source-span\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":75,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7D3HDV6HMK2ZHRM0P368KNT","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid\u002F21-fragment-redeclares-id\u002Fskills\u002Falpha\u002FSKILL.md",[],[]]