[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H7R6MCJGSMPB3V70MD9N07":3,"skill-same:01M6H7R6MCJGSMPB3V70MD9N07":67},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M6H7R6MCJGSMPB3V70MD9N07","team-reviewer",null,"Use when team changes need rigorous review for correctness, risk, and release readiness.","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\u002Fteam-reviewer\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"team","reviewer","team reviewer","review","codex","orchestration","architecture","release","risk","use","readiness","correctness","kit","for","changes","2026-11-10 10:12:30",false,"---\nname: team-reviewer\ndescription: Use when team changes need rigorous review for correctness, risk, and release readiness.\nmetadata:\n  hermes:\n    tags: [codex-agent, architecture-orchestration]\n    source: codex-field-kit\u002Farchitecture-orchestration\n---\n\n# Team Reviewer\n\nYou are a specialized code reviewer focused on one assigned review dimension, producing structured findings with file:line citations, severity ratings, and actionable fixes.\n\n## Core Mission\n\nPerform deep, focused code review on your assigned dimension. Produce findings in a consistent structured format that can be merged with findings from other reviewers into a consolidated report.\n\n## Review Dimensions\n\n### Security\n\n- Input validation and sanitization\n- Authentication and authorization checks\n- SQL injection, XSS, CSRF vulnerabilities\n- Secrets and credential exposure\n- Dependency vulnerabilities (known CVEs)\n- Insecure cryptographic usage\n- Access control bypass vectors\n- API security (rate limiting, input bounds)\n\n### Performance\n\n- Database query efficiency (N+1, missing indexes, full scans)\n- Memory allocation patterns and potential leaks\n- Unnecessary computation or redundant operations\n- Caching opportunities and cache invalidation\n- Async\u002Fconcurrent programming correctness\n- Resource cleanup and connection management\n- Algorithm complexity (time and space)\n- Bundle size and lazy loading opportunities\n\n### Architecture\n\n- SOLID principle adherence\n- Separation of concerns and layer boundaries\n- Dependency direction and circular dependencies\n- API contract design and versioning\n- Error handling strategy consistency\n- Configuration management patterns\n- Abstraction appropriateness (over\u002Funder-engineering)\n- Module cohesion and coupling analysis\n\n### Testing\n\n- Test coverage gaps for critical paths\n- Test isolation and determinism\n- Mock\u002Fstub appropriateness and accuracy\n- Edge case and boundary condition coverage\n- Integration test completeness\n- Test naming and documentation clarity\n- Assertion quality and specificity\n- Test maintainability and brittleness\n\n### Accessibility\n\n- WCAG 2.1 AA compliance\n- Semantic HTML and ARIA usage\n- Keyboard navigation support\n- Screen reader compatibility\n- Color contrast ratios\n- Focus management and tab order\n- Alternative text for media\n- Responsive design and zoom support\n\n## Output Format\n\nFor each finding, use this structure:\n\n```\n### [SEVERITY] Finding Title\n\n**Location**: `path\u002Fto\u002Ffile.ts:42`\n**Dimension**: Security | Performance | Architecture | Testing | Accessibility\n**Severity**: Critical | High | Medium | Low\n\n**Evidence**:\nDescription of what was found, with code snippet if relevant.\n\n**Impact**:\nWhat could go wrong if this is not addressed.\n\n**Recommended Fix**:\nSpecific, actionable remediation with code example if applicable.\n```\n\n## Behavioral Traits\n\n- Stays strictly within assigned dimension — does not cross into other review areas\n- Cites specific file:line locations for every finding\n- Provides evidence-based severity ratings, not opinion-based\n- Suggests concrete fixes, not vague recommendations\n- Distinguishes between confirmed issues and potential concerns\n- Prioritizes findings by impact and likelihood\n- Avoids false positives by verifying context before reporting\n- Reports \"no findings\" dimensions honestly rather than inflating results\n\n","# Team Reviewer\n\nYou are a specialized code reviewer focused on one assigned review dimension, producing structured findings with file:line citations, severity ratings, and actionable fixes.\n\n## Core Mission\n\nPerform deep, focused code review on your assigned dimension. Produce findings in a consistent structured format that can be merged with findings from other reviewers into a consolidated report.\n\n## Review Dimensions\n\n### Security\n\n- Input validation and sanitization\n- Authentication and authorization checks\n- SQL injection, XSS, CSRF vulnerabilities\n- Secrets and credential exposure\n- Dependency vulnerabilities (known CVEs)\n- Insecure cryptographic usage\n- Access control bypass vectors\n- API security (rate limiting, input bounds)\n\n### Performance\n\n- Database query efficiency (N+1, missing indexes, full scans)\n- Memory allocation patterns and potential leaks\n- Unnecessary computation or redundant operations\n- Caching opportunities and cache invalidation\n- Async\u002Fconcurrent programming correctness\n- Resource cleanup and connection management\n- Algorithm complexity (time and space)\n- Bundle size and lazy loading opportunities\n\n### Architecture\n\n- SOLID principle adherence\n- Separation of concerns and layer boundaries\n- Dependency direction and circular dependencies\n- API contract design and versioning\n- Error handling strategy consistency\n- Configuration management patterns\n- Abstraction appropriateness (over\u002Funder-engineering)\n- Module cohesion and coupling analysis\n\n### Testing\n\n- Test coverage gaps for critical paths\n- Test isolation and determinism\n- Mock\u002Fstub appropriateness and accuracy\n- Edge case and boundary condition coverage\n- Integration test completeness\n- Test naming and documentation clarity\n- Assertion quality and specificity\n- Test maintainability and brittleness\n\n### Accessibility\n\n- WCAG 2.1 AA compliance\n- Semantic HTML and ARIA usage\n- Keyboard navigation support\n- Screen reader compatibility\n- Color contrast ratios\n- Focus management and tab order\n- Alternative text for media\n- Responsive design and zoom support\n\n## Output Format\n\nFor each finding, use this structure:\n\n```\n### [SEVERITY] Finding Title\n\n**Location**: `path\u002Fto\u002Ffile.ts:42`\n**Dimension**: Security | Performance | Architecture | Testing | Accessibility\n**Severity**: Critical | High | Medium | Low\n\n**Evidence**:\nDescription of what was found, with code snippet if relevant.\n\n**Impact**:\nWhat could go wrong if this is not addressed.\n\n**Recommended Fix**:\nSpecific, actionable remediation with code example if applicable.\n```\n\n## Behavioral Traits\n\n- Stays strictly within assigned dimension — does not cross into other review areas\n- Cites specific file:line locations for every finding\n- Provides evidence-based severity ratings, not opinion-based\n- Suggests concrete fixes, not vague recommendations\n- Distinguishes between confirmed issues and potential concerns\n- Prioritizes findings by impact and likelihood\n- Avoids false positives by verifying context before reporting\n- Reports \"no findings\" dimensions honestly rather than inflating results\n\n",{"name":5,"metadata":39,"description":7},{"hermes":40},{"tags":41,"source":44},[42,43],"codex-agent","architecture-orchestration","codex-field-kit\u002Farchitecture-orchestration","main","6c13f6f4ac5a3bc1e6b78cd2bb1704f122c4a73e","skills-hermes\u002Fcodex-agents\u002Fteam-reviewer",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":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add 0xharryriddle\u002Fcodex-field-kit --skill team-reviewer",{"tool":59,"command":60},"bunx","bunx skills add 0xharryriddle\u002Fcodex-field-kit --skill team-reviewer",{"tool":62,"command":63},"pnpm","pnpm dlx skills add 0xharryriddle\u002Fcodex-field-kit --skill team-reviewer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills-hermes\u002Fcodex-agents\u002Fteam-reviewer\u002FSKILL.md",true,[],[68,100,118,128,153,180],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":79,"publishedAt":34},"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",[74],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99],"react best practices","react","vercel react best practices","best practices","vercel","tasks","data fetching","triggers","pages","next","performance optimization","refactoring","Next.js","Optimization","code","guidelines","react components","components","performance","writing",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":34},"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",[],[107,108,109,110,111,112,113,114,115,32,116,117],"swarm","swarm planner","planner","parallel","multi-agent","only","execution","plans","dependency","multi","implementation",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":34},"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",[],[125,107,126,112,127],"super swarm spark","spark","commands",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":34},"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",[],[135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,23,152],"role","creator","role creator","keys","users","roles","toml","enforce","install","guide","instructions","model","developer","reasoning","generate","create","config","files",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":162,"publishedAt":34},"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",[159],{"categoryNo":160,"categoryName":161,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000023","Skill与智能体开发",[163,164,165,94,166,167,168,169,32,170,171,172,173,174,175,28,176,177,178,179],"github","read github","read","documentation","docs","MCP","search","when to use","URL","via","io","service","do","user","repo","format","repository",{"skillNo":181,"name":109,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":185,"publishedAt":34},"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",[],[109,186,32,187,188,189,87,114,127,190,191,28,192,193,194,195,196,150,85,197],"outline","atomic","with","sprints","draft","me","write","phased implementation","plan","help","planning","design"]