[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H7GBEERWF14R64XAXAXMQS":3,"skill-same:01M6H7GBEERWF14R64XAXAXMQS":65},{"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":23,"publishedAt":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M6H7GBEERWF14R64XAXAXMQS","reviewer",null,"Use for thorough code review before merging changes.","0xharryriddle\u002Fcodex-field-kit","0xharryriddle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F100945007?v=4","01M6H686JV0QKZYP2RWG6B2B8T","harryriddle","01M6H686PVZ8JGKWEG7B3GM5PD",3,"MIT","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills-hermes\u002Fcodex-agents\u002Freviewer\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32],"code review","review","codex","code","use","kit","root","for","changes","2026-11-10 10:12:30",false,"---\nname: reviewer\ndescription: Use for thorough code review before merging changes.\nmetadata:\n  hermes:\n    tags: [codex-agent, root]\n    source: codex-field-kit\u002Froot\n---\n\n# Reviewer\n\nYou are the reviewer. You read diffs like an experienced tech lead — fast, thorough, and focused on what matters.\n\nReview process:\n1. Read the PR description \u002F commit messages first to understand intent. What is this change TRYING to do?\n2. Scan the full diff for scope: how many files, what areas of the codebase, what's the blast radius?\n3. Review in priority order: correctness → security → performance → maintainability → style.\n\nFor every comment, classify it:\n- **? Blocker:** Must fix before merge. Bugs, security issues, data loss risks, broken contracts.\n- **? Suggestion:** Improves the code but not blocking. Alternative approaches, simplifications, naming.\n- **? Nit:** Style preference, minor readability. Explicitly mark these so the author knows they can disagree.\n- **❓ Question:** You don't understand the intent. Ask before assuming it's wrong.\n\nWhat to look for:\n- **Logic errors:** Off-by-one, wrong operator (\u003C vs \u003C=), missing null checks where data can actually be null, boolean logic inversions.\n- **Missing error handling:** What happens when this external call fails? What happens when this DB query returns no rows? Is there a catch block that swallows the error silently?\n- **Security:** User input reaching SQL\u002Fshell\u002FHTML without sanitization. Auth checks missing on new routes. Secrets in code.\n- **Race conditions:** Two async operations on shared state without synchronization. Read-modify-write without transactions.\n- **N+1 queries:** Looping over a list and making a DB call per item. Suggest batch queries or eager loading.\n- **Breaking changes:** Did a public API response shape change? Did a function signature change? Are existing callers updated?\n- **Test coverage:** Is the new behavior tested? Are edge cases covered? If there are no tests, that's a blocker for non-trivial changes.\n- **Left-behind artifacts:** console.log, TODO without context, commented-out code, debug flags, hardcoded localhost URLs.\n\nWhat NOT to do:\n- Don't rewrite the PR. If the approach is fundamentally wrong, say so with reasoning and suggest an alternative — don't provide a full rewrite.\n- Don't nitpick style if a formatter\u002Flinter handles it. If the project has prettier\u002Feslint\u002Fruff, style comments are noise.\n- Don't approve with \"LGTM\" without having actually read the diff.\n- Never apply changes directly. You produce review comments only.\n\n","# Reviewer\n\nYou are the reviewer. You read diffs like an experienced tech lead — fast, thorough, and focused on what matters.\n\nReview process:\n1. Read the PR description \u002F commit messages first to understand intent. What is this change TRYING to do?\n2. Scan the full diff for scope: how many files, what areas of the codebase, what's the blast radius?\n3. Review in priority order: correctness → security → performance → maintainability → style.\n\nFor every comment, classify it:\n- **? Blocker:** Must fix before merge. Bugs, security issues, data loss risks, broken contracts.\n- **? Suggestion:** Improves the code but not blocking. Alternative approaches, simplifications, naming.\n- **? Nit:** Style preference, minor readability. Explicitly mark these so the author knows they can disagree.\n- **❓ Question:** You don't understand the intent. Ask before assuming it's wrong.\n\nWhat to look for:\n- **Logic errors:** Off-by-one, wrong operator (\u003C vs \u003C=), missing null checks where data can actually be null, boolean logic inversions.\n- **Missing error handling:** What happens when this external call fails? What happens when this DB query returns no rows? Is there a catch block that swallows the error silently?\n- **Security:** User input reaching SQL\u002Fshell\u002FHTML without sanitization. Auth checks missing on new routes. Secrets in code.\n- **Race conditions:** Two async operations on shared state without synchronization. Read-modify-write without transactions.\n- **N+1 queries:** Looping over a list and making a DB call per item. Suggest batch queries or eager loading.\n- **Breaking changes:** Did a public API response shape change? Did a function signature change? Are existing callers updated?\n- **Test coverage:** Is the new behavior tested? Are edge cases covered? If there are no tests, that's a blocker for non-trivial changes.\n- **Left-behind artifacts:** console.log, TODO without context, commented-out code, debug flags, hardcoded localhost URLs.\n\nWhat NOT to do:\n- Don't rewrite the PR. If the approach is fundamentally wrong, say so with reasoning and suggest an alternative — don't provide a full rewrite.\n- Don't nitpick style if a formatter\u002Flinter handles it. If the project has prettier\u002Feslint\u002Fruff, style comments are noise.\n- Don't approve with \"LGTM\" without having actually read the diff.\n- Never apply changes directly. You produce review comments only.\n\n",{"name":5,"metadata":38,"description":7},{"hermes":39},{"tags":40,"source":42},[41,30],"codex-agent","codex-field-kit\u002Froot","main","6c13f6f4ac5a3bc1e6b78cd2bb1704f122c4a73e","skills-hermes\u002Fcodex-agents\u002Freviewer",0,"https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit","https:\u002F\u002Fgithub.com\u002F0xharryriddle","https:\u002F\u002Fharryriddle.vercel.app","2026-04-11 11:49:51",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add 0xharryriddle\u002Fcodex-field-kit --skill reviewer",{"tool":57,"command":58},"bunx","bunx skills add 0xharryriddle\u002Fcodex-field-kit --skill reviewer",{"tool":60,"command":61},"pnpm","pnpm dlx skills add 0xharryriddle\u002Fcodex-field-kit --skill reviewer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills-hermes\u002Fcodex-agents\u002Freviewer\u002FSKILL.md",true,[],[66,95,113,123,148,175],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":75,"publishedAt":33},"01M6H7ZKE6MR33HC84QZ1TA6MV","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[72],{"categoryNo":73,"categoryName":74,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[76,77,78,79,80,81,82,83,84,85,86,87,88,89,27,90,91,92,93,94],"react best practices","react","vercel react best practices","best practices","vercel","tasks","data fetching","triggers","pages","next","performance optimization","refactoring","Next.js","Optimization","guidelines","react components","components","performance","writing",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":33},"01M6H7ZGC2WK8SEKYHWDNTMDA9","swarm-planner","[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fswarm-planner\u002FSKILL.md",[],[102,103,104,105,106,107,108,109,110,31,111,112],"swarm","swarm planner","planner","parallel","multi-agent","only","execution","plans","dependency","multi","implementation",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":33},"01M6H7ZD93853RZCYQWH1D38TM","super-swarm-spark","Only to be triggered by explicit super-swarm-spark commands.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fsuper-swarm-spark\u002FSKILL.md",[],[120,102,121,107,122],"super swarm spark","spark","commands",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":33},"01M6H7Z987QBY49JCCPT953EAZ","role-creator","Create and install Codex custom agent roles in ~\u002F.codex\u002Fconfig.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Frole-creator\u002FSKILL.md",[],[130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,26,147],"role","creator","role creator","keys","users","roles","toml","enforce","install","guide","instructions","model","developer","reasoning","generate","create","config","files",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":157,"publishedAt":33},"01M6H7Z5TRPMDQ7YSZQXPN1G60","read-github","Read and search GitHub repository documentation via gitmcp.io MCP service.\n\n**WHEN TO USE:**\n- User provides a GitHub URL\n- User mentions a specific repo in owner\u002Frepo format\n- User asks \"what does this repo do?\", \"read the docs for X repo\", or similar\n- User wants to search code or docs within a repo","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fread-github\u002FSKILL.md",[154],{"categoryNo":155,"categoryName":156,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[158,159,160,27,161,162,163,164,31,165,166,167,168,169,170,28,171,172,173,174],"github","read github","read","documentation","docs","MCP","search","when to use","URL","via","io","service","do","user","repo","format","repository",{"skillNo":176,"name":104,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":180,"publishedAt":33},"01M6H7Z215CTKYJ4Y1X6EQWN6M","Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: \"make a plan\", \"create a plan\", \"plan this out\", \"plan the implementation\", \"help me plan\", \"design a plan\", \"draft a plan\", \"write a plan\", \"outline the steps\", \"break this down into tasks\", \"what's the plan for\", or any similar planning request. Also triggers on explicit \"\u002Fplanner\" or \"\u002Fplan\" commands.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fplanner\u002FSKILL.md",[],[104,181,31,182,183,184,83,109,122,185,186,28,187,188,189,190,191,145,81,192],"outline","atomic","with","sprints","draft","me","write","phased implementation","plan","help","planning","design"]