[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XDRXY5DFF3NGTN13BTSHR3":3,"skill-same:01M6XDRXY5DFF3NGTN13BTSHR3":59},{"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":28,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":14,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M6XDRXY5DFF3NGTN13BTSHR3","code-review",null,"Run a comprehensive code review","sapsapshen\u002Fai-memory-router","sapsapshen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20347959?v=4","01M6XDQEF1DP50DKF37H81J3J5","shenmian","01M6XDQEJPE41Y3DT2763X8ZJN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcodex\u002Fcode-review\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33],"code review","review","code","run","comprehensive code review","2026-11-10 10:12:30",false,"---\nname: code-review\ndescription: Run a comprehensive code review\n---\n\n# Code Review Skill\n\nConduct a thorough code review for quality, security, and maintainability with severity-rated feedback.\n\n## When to Use\n\nThis skill activates when:\n- User requests \"review this code\", \"code review\"\n- Before merging a pull request\n- After implementing a major feature\n- User wants quality assessment\n\n## What It Does\n\n## GPT-5.4 Guidance Alignment\n\n- Default to concise, evidence-dense progress and completion reporting unless the user or risk level requires more detail.\n- Treat newer user task updates as local overrides for the active workflow branch while preserving earlier non-conflicting constraints.\n- If correctness depends on additional inspection, retrieval, execution, or verification, keep using the relevant tools until the review is grounded.\n- Continue through clear, low-risk, reversible next steps automatically; ask only when the next step is materially branching, destructive, or preference-dependent.\n\nDelegates to the `code-reviewer` agent (THOROUGH tier) for deep analysis:\n\n1. **Identify Changes**\n   - Run `git diff` to find changed files\n   - Determine scope of review (specific files or entire PR)\n\n2. **Review Categories**\n   - **Security** - Hardcoded secrets, injection risks, XSS, CSRF\n   - **Code Quality** - Function size, complexity, nesting depth\n   - **Performance** - Algorithm efficiency, N+1 queries, caching\n   - **Best Practices** - Naming, documentation, error handling\n   - **Maintainability** - Duplication, coupling, testability\n\n3. **Severity Rating**\n   - **CRITICAL** - Security vulnerability (must fix before merge)\n   - **HIGH** - Bug or major code smell (should fix before merge)\n   - **MEDIUM** - Minor issue (fix when possible)\n   - **LOW** - Style\u002Fsuggestion (consider fixing)\n\n4. **Specific Recommendations**\n   - File:line locations for each issue\n   - Concrete fix suggestions\n   - Code examples where applicable\n\n## Agent Delegation\n\n```\ndelegate(\n  role=\"code-reviewer\",\n  tier=\"THOROUGH\",\n  prompt=\"CODE REVIEW TASK\n\nReview code changes for quality, security, and maintainability.\n\nScope: [git diff or specific files]\n\nReview Checklist:\n- Security vulnerabilities (OWASP Top 10)\n- Code quality (complexity, duplication)\n- Performance issues (N+1, inefficient algorithms)\n- Best practices (naming, documentation, error handling)\n- Maintainability (coupling, testability)\n\nOutput: Code review report with:\n- Files reviewed count\n- Issues by severity (CRITICAL, HIGH, MEDIUM, LOW)\n- Specific file:line locations\n- Fix recommendations\n- Approval recommendation (APPROVE \u002F REQUEST CHANGES \u002F COMMENT)\"\n)\n```\n\n## External Model Consultation (Preferred)\n\nThe code-reviewer agent SHOULD consult Codex for cross-validation.\n\n### Protocol\n1. **Form your OWN review FIRST** - Complete the review independently\n2. **Consult for validation** - Cross-check findings with Codex\n3. **Critically evaluate** - Never blindly adopt external findings\n4. **Graceful fallback** - Never block if tools unavailable\n\n### When to Consult\n- Security-sensitive code changes\n- Complex architectural patterns\n- Unfamiliar codebases or languages\n- High-stakes production code\n\n### When to Skip\n- Simple refactoring\n- Well-understood patterns\n- Time-critical reviews\n- Small, isolated changes\n\n### Tool Usage\nBefore first MCP tool use, call `ToolSearch(\"mcp\")` to discover deferred MCP tools.\nUse `mcp__x__ask_codex` with `agent_role: \"code-reviewer\"`.\nIf ToolSearch finds no MCP tools, fall back to the `code-reviewer` agent.\n\n**Note:** Codex calls can take up to 1 hour. Consider the review timeline before consulting.\n\n## Output Format\n\n```\nCODE REVIEW REPORT\n==================\n\nFiles Reviewed: 8\nTotal Issues: 15\n\nCRITICAL (0)\n-----------\n(none)\n\nHIGH (3)\n--------\n1. src\u002Fapi\u002Fauth.ts:42\n   Issue: User input not sanitized before SQL query\n   Risk: SQL injection vulnerability\n   Fix: Use parameterized queries or ORM\n\n2. src\u002Fcomponents\u002FUserProfile.tsx:89\n   Issue: Password displayed in plain text in logs\n   Risk: Credential exposure\n   Fix: Remove password from log statements\n\n3. src\u002Futils\u002Fvalidation.ts:15\n   Issue: Email regex allows invalid formats\n   Risk: Accepts malformed emails\n   Fix: Use proven email validation library\n\nMEDIUM (7)\n----------\n...\n\nLOW (5)\n-------\n...\n\nRECOMMENDATION: REQUEST CHANGES\n\nCritical security issues must be addressed before merge.\n```\n\n## Review Checklist\n\nThe code-reviewer agent checks:\n\n### Security\n- [ ] No hardcoded secrets (API keys, passwords, tokens)\n- [ ] All user inputs sanitized\n- [ ] SQL\u002FNoSQL injection prevention\n- [ ] XSS prevention (escaped outputs)\n- [ ] CSRF protection on state-changing operations\n- [ ] Authentication\u002Fauthorization properly enforced\n\n### Code Quality\n- [ ] Functions \u003C 50 lines (guideline)\n- [ ] Cyclomatic complexity \u003C 10\n- [ ] No deeply nested code (> 4 levels)\n- [ ] No duplicate logic (DRY principle)\n- [ ] Clear, descriptive naming\n\n### Performance\n- [ ] No N+1 query patterns\n- [ ] Appropriate caching where applicable\n- [ ] Efficient algorithms (avoid O(n²) when O(n) possible)\n- [ ] No unnecessary re-renders (React\u002FVue)\n\n### Best Practices\n- [ ] Error handling present and appropriate\n- [ ] Logging at appropriate levels\n- [ ] Documentation for public APIs\n- [ ] Tests for critical paths\n- [ ] No commented-out code\n\n## Approval Criteria\n\n**APPROVE** - No CRITICAL or HIGH issues, minor improvements only\n**REQUEST CHANGES** - CRITICAL or HIGH issues present\n**COMMENT** - Only LOW\u002FMEDIUM issues, no blocking concerns\n\n\n## Scenario Examples\n\n**Good:** The user says `continue` after the workflow already has a clear next step. Continue the current branch of work instead of restarting or re-asking the same question.\n\n**Good:** The user changes only the output shape or downstream delivery step (for example `make a PR`). Preserve earlier non-conflicting workflow constraints and apply the update locally.\n\n**Bad:** The user says `continue`, and the workflow restarts discovery or stops before the missing verification\u002Fevidence is gathered.\n\n## Use with Other Skills\n\n**With Team:**\n```\n\u002Fteam \"review recent auth changes and report findings\"\n```\nIncludes coordinated review execution across specialized agents.\n\n**With Ralph:**\n```\n\u002Fralph code-review then fix all issues\n```\nReview code, get feedback, fix until approved.\n\n**With Ultrawork:**\n```\n\u002Fultrawork review all files in src\u002F\n```\nParallel code review across multiple files.\n\n## Best Practices\n\n- **Review early** - Catch issues before they compound\n- **Review often** - Small, frequent reviews better than huge ones\n- **Address CRITICAL\u002FHIGH first** - Fix security and bugs immediately\n- **Consider context** - Some \"issues\" may be intentional trade-offs\n- **Learn from reviews** - Use feedback to improve coding practices\n","# Code Review Skill\n\nConduct a thorough code review for quality, security, and maintainability with severity-rated feedback.\n\n## When to Use\n\nThis skill activates when:\n- User requests \"review this code\", \"code review\"\n- Before merging a pull request\n- After implementing a major feature\n- User wants quality assessment\n\n## What It Does\n\n## GPT-5.4 Guidance Alignment\n\n- Default to concise, evidence-dense progress and completion reporting unless the user or risk level requires more detail.\n- Treat newer user task updates as local overrides for the active workflow branch while preserving earlier non-conflicting constraints.\n- If correctness depends on additional inspection, retrieval, execution, or verification, keep using the relevant tools until the review is grounded.\n- Continue through clear, low-risk, reversible next steps automatically; ask only when the next step is materially branching, destructive, or preference-dependent.\n\nDelegates to the `code-reviewer` agent (THOROUGH tier) for deep analysis:\n\n1. **Identify Changes**\n   - Run `git diff` to find changed files\n   - Determine scope of review (specific files or entire PR)\n\n2. **Review Categories**\n   - **Security** - Hardcoded secrets, injection risks, XSS, CSRF\n   - **Code Quality** - Function size, complexity, nesting depth\n   - **Performance** - Algorithm efficiency, N+1 queries, caching\n   - **Best Practices** - Naming, documentation, error handling\n   - **Maintainability** - Duplication, coupling, testability\n\n3. **Severity Rating**\n   - **CRITICAL** - Security vulnerability (must fix before merge)\n   - **HIGH** - Bug or major code smell (should fix before merge)\n   - **MEDIUM** - Minor issue (fix when possible)\n   - **LOW** - Style\u002Fsuggestion (consider fixing)\n\n4. **Specific Recommendations**\n   - File:line locations for each issue\n   - Concrete fix suggestions\n   - Code examples where applicable\n\n## Agent Delegation\n\n```\ndelegate(\n  role=\"code-reviewer\",\n  tier=\"THOROUGH\",\n  prompt=\"CODE REVIEW TASK\n\nReview code changes for quality, security, and maintainability.\n\nScope: [git diff or specific files]\n\nReview Checklist:\n- Security vulnerabilities (OWASP Top 10)\n- Code quality (complexity, duplication)\n- Performance issues (N+1, inefficient algorithms)\n- Best practices (naming, documentation, error handling)\n- Maintainability (coupling, testability)\n\nOutput: Code review report with:\n- Files reviewed count\n- Issues by severity (CRITICAL, HIGH, MEDIUM, LOW)\n- Specific file:line locations\n- Fix recommendations\n- Approval recommendation (APPROVE \u002F REQUEST CHANGES \u002F COMMENT)\"\n)\n```\n\n## External Model Consultation (Preferred)\n\nThe code-reviewer agent SHOULD consult Codex for cross-validation.\n\n### Protocol\n1. **Form your OWN review FIRST** - Complete the review independently\n2. **Consult for validation** - Cross-check findings with Codex\n3. **Critically evaluate** - Never blindly adopt external findings\n4. **Graceful fallback** - Never block if tools unavailable\n\n### When to Consult\n- Security-sensitive code changes\n- Complex architectural patterns\n- Unfamiliar codebases or languages\n- High-stakes production code\n\n### When to Skip\n- Simple refactoring\n- Well-understood patterns\n- Time-critical reviews\n- Small, isolated changes\n\n### Tool Usage\nBefore first MCP tool use, call `ToolSearch(\"mcp\")` to discover deferred MCP tools.\nUse `mcp__x__ask_codex` with `agent_role: \"code-reviewer\"`.\nIf ToolSearch finds no MCP tools, fall back to the `code-reviewer` agent.\n\n**Note:** Codex calls can take up to 1 hour. Consider the review timeline before consulting.\n\n## Output Format\n\n```\nCODE REVIEW REPORT\n==================\n\nFiles Reviewed: 8\nTotal Issues: 15\n\nCRITICAL (0)\n-----------\n(none)\n\nHIGH (3)\n--------\n1. src\u002Fapi\u002Fauth.ts:42\n   Issue: User input not sanitized before SQL query\n   Risk: SQL injection vulnerability\n   Fix: Use parameterized queries or ORM\n\n2. src\u002Fcomponents\u002FUserProfile.tsx:89\n   Issue: Password displayed in plain text in logs\n   Risk: Credential exposure\n   Fix: Remove password from log statements\n\n3. src\u002Futils\u002Fvalidation.ts:15\n   Issue: Email regex allows invalid formats\n   Risk: Accepts malformed emails\n   Fix: Use proven email validation library\n\nMEDIUM (7)\n----------\n...\n\nLOW (5)\n-------\n...\n\nRECOMMENDATION: REQUEST CHANGES\n\nCritical security issues must be addressed before merge.\n```\n\n## Review Checklist\n\nThe code-reviewer agent checks:\n\n### Security\n- [ ] No hardcoded secrets (API keys, passwords, tokens)\n- [ ] All user inputs sanitized\n- [ ] SQL\u002FNoSQL injection prevention\n- [ ] XSS prevention (escaped outputs)\n- [ ] CSRF protection on state-changing operations\n- [ ] Authentication\u002Fauthorization properly enforced\n\n### Code Quality\n- [ ] Functions \u003C 50 lines (guideline)\n- [ ] Cyclomatic complexity \u003C 10\n- [ ] No deeply nested code (> 4 levels)\n- [ ] No duplicate logic (DRY principle)\n- [ ] Clear, descriptive naming\n\n### Performance\n- [ ] No N+1 query patterns\n- [ ] Appropriate caching where applicable\n- [ ] Efficient algorithms (avoid O(n²) when O(n) possible)\n- [ ] No unnecessary re-renders (React\u002FVue)\n\n### Best Practices\n- [ ] Error handling present and appropriate\n- [ ] Logging at appropriate levels\n- [ ] Documentation for public APIs\n- [ ] Tests for critical paths\n- [ ] No commented-out code\n\n## Approval Criteria\n\n**APPROVE** - No CRITICAL or HIGH issues, minor improvements only\n**REQUEST CHANGES** - CRITICAL or HIGH issues present\n**COMMENT** - Only LOW\u002FMEDIUM issues, no blocking concerns\n\n\n## Scenario Examples\n\n**Good:** The user says `continue` after the workflow already has a clear next step. Continue the current branch of work instead of restarting or re-asking the same question.\n\n**Good:** The user changes only the output shape or downstream delivery step (for example `make a PR`). Preserve earlier non-conflicting workflow constraints and apply the update locally.\n\n**Bad:** The user says `continue`, and the workflow restarts discovery or stops before the missing verification\u002Fevidence is gathered.\n\n## Use with Other Skills\n\n**With Team:**\n```\n\u002Fteam \"review recent auth changes and report findings\"\n```\nIncludes coordinated review execution across specialized agents.\n\n**With Ralph:**\n```\n\u002Fralph code-review then fix all issues\n```\nReview code, get feedback, fix until approved.\n\n**With Ultrawork:**\n```\n\u002Fultrawork review all files in src\u002F\n```\nParallel code review across multiple files.\n\n## Best Practices\n\n- **Review early** - Catch issues before they compound\n- **Review often** - Small, frequent reviews better than huge ones\n- **Address CRITICAL\u002FHIGH first** - Fix security and bugs immediately\n- **Consider context** - Some \"issues\" may be intentional trade-offs\n- **Learn from reviews** - Use feedback to improve coding practices\n",{"name":5,"description":7},"main","7a38d8e7073e61c16eda85681cb32fb68a8657a5","skills-store\u002Fcodex\u002Fcode-review","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router","https:\u002F\u002Fgithub.com\u002Fsapsapshen","2026-04-14 21:12:12",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add sapsapshen\u002Fai-memory-router --skill code-review",{"tool":51,"command":52},"bunx","bunx skills add sapsapshen\u002Fai-memory-router --skill code-review",{"tool":54,"command":55},"pnpm","pnpm dlx skills add sapsapshen\u002Fai-memory-router --skill code-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcodex\u002Fcode-review\u002FSKILL.md",true,[],[60,82,108,118,131,148],{"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":69,"publishedAt":34},"01M71ATQRKG48SH06FQ697T5G9","wechat-search","Search WeChat Official Account articles using OpenClaw's web search and fetch capabilities with compliance-focused design.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fwechat-search-release\u002FSKILL.md",[66],{"categoryNo":67,"categoryName":68,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务",[70,71,72,73,74,75,76,77,78,79,80,81],"wechat search","wechat","search","capabilities","openclaw","design","web search","compliance","web","official","fetch","with",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":34},"01M71ATNAVGZB35PFYM2GC5N00","trend-tap","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend tap', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-tap\u002FSKILL.md",[],[89,90,91,92,93,94,72,95,96,97,98,99,100,101,102,103,104,105,106,107],"trend","trend tap","tap","api keys","Bash","time","trending","hacker","aggregator","do","when","brew","live","data","google","install","read","across","api",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":34},"01M71ATJ9AM5KM15AA8PS302EB","trend-radar","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend pulse', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-radar\u002FSKILL.md",[],[115,116,89,100,101,102,103,93,72,105,117,106,107,99,97,96,95,104,94,92],"trend radar","radar","pulse",{"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},"01M71ATGF095N3EJM9G8SD0BB5","tech-news-daily","每日科技新闻汇——从全球多个 RSS 源抓取最新科技新闻，翻译（英→中）、去重、排版成每日简报。当用户询问科技新闻、科技新鲜事、每日科技、技术动态、Daily Tech News 或类似表达时触发此技能。","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftech-news-daily\u002FSKILL.md",[],[125,126,127,128,129,130],"news","tech","tech news daily","daily","rss","翻译",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":140,"publishedAt":34},"01M71ATFAEAMQ17M70NQNY7SR8","summarize","Summarize URLs or files with the summarize CLI (web, PDFs, images, audio, YouTube).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsummarize\u002FSKILL.md",[137],{"categoryNo":138,"categoryName":139,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",[133,78,141,142,143,81,100,144,145,146,91,147,104],"Audio","cli","youtube","images","https","files","pdfs",{"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":154,"publishedAt":34},"01M71ATDNS3R0M4H936PACQAWZ","sonoscli","Control Sonos speakers (discover\u002Fstatus\u002Fplay\u002Fvolume\u002Fgroup).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsonoscli\u002FSKILL.md",[],[150,155,156,157,104,158,145,159,160,161,162,163],"status","play","go","latest","github","discover","control","cmd","volume"]