[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KVXVG170C7SJ5EJ41A2HDT":3,"skill-same:01M6KVXVG170C7SJ5EJ41A2HDT":64},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M6KVXVG170C7SJ5EJ41A2HDT","cc-review",null,"Use Claude Code CLI to review pull requests with Nuvel OrgMemory context for team standards alignment.","Folken2\u002Fnuvel","Folken2","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F175213316?v=4","01M6KVPA04RKNPCC04H2G96FAS","Albert Folch","01M6KVPA43VNTA4PXSEB1TCD81",2,"MIT","https:\u002F\u002Fgithub.com\u002FFolken2\u002Fnuvel\u002Fblob\u002Fmain\u002Fplugins\u002Fclaude-code-plugin\u002Fskills\u002Fcc-review\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"cc review","cc","review","standards","nuvel","for","requests","with","claude code cli","alignment","use","context","team","pull","code","pull requests","cli","2026-11-10 10:12:30",false,"---\nname: cc-review\ndescription: Use Claude Code CLI to review pull requests with Nuvel OrgMemory context for team standards alignment.\n---\n\n# Claude Code CLI PR Review\n\n## Trigger Conditions\n- Pull request is ready for review\n- Need OrgMemory-informed code review\n- Pre-merge quality gate automation\n- Pair-review with a human reviewer for critical changes\n\n## Prerequisites\n- Claude Code CLI installed and configured (`cc-setup` skill)\n- Nuvel OrgMemory MCP server connected\n- GitHub CLI (`gh`) installed and authenticated\n- CLAUDE.md with project conventions\n\n## Steps\n\n### 1. Fetch and Checkout PR\n\n```bash\nPR_NUMBER=\"\u003Cnumber>\"\n\n# View PR details\ngh pr view $PR_NUMBER --json number,title,body,baseRefName,headRefName,additions,deletions,files\n\n# Checkout locally\ngh pr checkout $PR_NUMBER\n```\n\n### 2. Gather OrgMemory Context\n\n```bash\nclaude -p \"For PR #${PR_NUMBER}, search nuvel-orgmemory for: \\\n  1. Architecture decisions about the components modified in this PR \\\n  2. Coding standards relevant to the languages\u002Fframeworks used \\\n  3. Any past incidents or bugs related to these files \\\n  4. Team conventions for the patterns used \\\n  Output a structured context summary.\"\n```\n\n### 3. Run Comprehensive Review\n\n```bash\nclaude -p \"Review PR #${PR_NUMBER} using the following framework:\n\n## OrgMemory Context (from previous search):\n\u003Cpaste OrgMemory context summary here>\n\n## Review Framework:\n### Security\n- Injection vulnerabilities (SQL, XSS, command)\n- Exposed secrets or API keys\n- Authentication\u002Fauthorization bypasses\n- Unsafe deserialization or eval\n\n### Performance\n- N+1 queries and unnecessary database calls\n- Missing indexes or inefficient queries\n- Memory leaks or unbounded growth\n- Blocking operations in async contexts\n\n### Correctness\n- Edge cases: null\u002Fundefined, empty collections, boundary values\n- Error handling: proper propagation, user-friendly messages\n- Race conditions and concurrency issues\n- Type safety violations\n\n### Architecture (cross-reference with OrgMemory)\n- Does this follow existing patterns?\n- Are new abstractions consistent with the codebase?\n- Is there unnecessary coupling?\n- Are there violations of established decisions?\n\n### Testing\n- Coverage of new code paths (happy path, error path, edge cases)\n- Test quality (meaningful assertions, not just coverage metrics)\n- Integration test coverage for API changes\n- Are mocking practices appropriate?\n\n### Maintainability\n- Clear naming and documentation\n- Complexity hotspots (cyclomatic complexity, deep nesting)\n- TODO\u002FFIXME comments that should be resolved\n- Breaking changes properly flagged\n\n## Output Format:\nGenerate a review in this structure:\n\n### Summary\nBrief overview of the changes and overall assessment.\n\n### Critical Issues (must fix before merge)\n- [ ] Issue 1: \u003Cdescription> (file:line)\n- [ ] Issue 2: \u003Cdescription> (file:line)\n\n### Warnings (should fix)\n- [ ] Warning 1: \u003Cdescription> (file:line)\n\n### Suggestions (nice to have)\n- Suggestion 1: \u003Cdescription>\n\n### OrgMemory Alignment\n- ✅ Aligned: \u003Cdecision\u002Fpattern followed>\n- ⚠️ Deviation: \u003Cdecision not followed, with justification if valid>\"\n```\n\n### 4. Post Review\n\nBased on findings:\n\n```bash\n# If no critical issues:\ngh pr review $PR_NUMBER --approve \\\n  --body \"## Automated Review by Claude Code + Nuvel OrgMemory\n\n$(cat review-output.md)\n\nReviewed against OrgMemory standards and project conventions.\"\n\n# If issues found:\ngh pr review $PR_NUMBER --request-changes \\\n  --body \"$(cat review-output.md)\"\n\n# For comments only:\ngh pr review $PR_NUMBER --comment \\\n  --body \"$(cat review-output.md)\"\n```\n\n### 5. Post-Review Actions\n\n```bash\n# If new patterns or anti-patterns were found:\nclaude -p \"Update nuvel-orgmemory with review insights from PR #${PR_NUMBER}: \\\n  - Any new patterns that should be documented \\\n  - Anti-patterns to avoid in future \\\n  - Updated component documentation if architecture changed\"\n```\n\n## Review Severity Guidelines\n\n| Severity | Criteria | Action |\n|----------|----------|--------|\n| Critical | Security vulnerability, data loss risk, breaks existing functionality | Request changes, block merge |\n| Warning | Performance regression, missing error handling, test gap | Request changes or comment |\n| Suggestion | Code style, naming, minor optimizations | Comment, non-blocking |\n\n## Pitfalls\n- **Review scope creep**: Focus review on the PR's stated purpose. Avoid suggesting unrelated refactors.\n- **OrgMemory staleness**: If team practices evolved but OrgMemory is outdated, note the discrepancy rather than blocking on it.\n- **Large PRs**: For PRs over 400 lines, request the author to split or focus review on the most critical files.\n- **False confidence**: Claude Code may miss subtle bugs. Critical PRs should always have human review in addition to automated review.\n\n## Verification\n1. Review posted on the PR: `gh pr view $PR_NUMBER --comments`\n2. All critical issues have corresponding comments\n3. Review references specific OrgMemory decisions\u002Fpatterns\n4. Post-review OrgMemory update completed (if applicable)","# Claude Code CLI PR Review\n\n## Trigger Conditions\n- Pull request is ready for review\n- Need OrgMemory-informed code review\n- Pre-merge quality gate automation\n- Pair-review with a human reviewer for critical changes\n\n## Prerequisites\n- Claude Code CLI installed and configured (`cc-setup` skill)\n- Nuvel OrgMemory MCP server connected\n- GitHub CLI (`gh`) installed and authenticated\n- CLAUDE.md with project conventions\n\n## Steps\n\n### 1. Fetch and Checkout PR\n\n```bash\nPR_NUMBER=\"\u003Cnumber>\"\n\n# View PR details\ngh pr view $PR_NUMBER --json number,title,body,baseRefName,headRefName,additions,deletions,files\n\n# Checkout locally\ngh pr checkout $PR_NUMBER\n```\n\n### 2. Gather OrgMemory Context\n\n```bash\nclaude -p \"For PR #${PR_NUMBER}, search nuvel-orgmemory for: \\\n  1. Architecture decisions about the components modified in this PR \\\n  2. Coding standards relevant to the languages\u002Fframeworks used \\\n  3. Any past incidents or bugs related to these files \\\n  4. Team conventions for the patterns used \\\n  Output a structured context summary.\"\n```\n\n### 3. Run Comprehensive Review\n\n```bash\nclaude -p \"Review PR #${PR_NUMBER} using the following framework:\n\n## OrgMemory Context (from previous search):\n\u003Cpaste OrgMemory context summary here>\n\n## Review Framework:\n### Security\n- Injection vulnerabilities (SQL, XSS, command)\n- Exposed secrets or API keys\n- Authentication\u002Fauthorization bypasses\n- Unsafe deserialization or eval\n\n### Performance\n- N+1 queries and unnecessary database calls\n- Missing indexes or inefficient queries\n- Memory leaks or unbounded growth\n- Blocking operations in async contexts\n\n### Correctness\n- Edge cases: null\u002Fundefined, empty collections, boundary values\n- Error handling: proper propagation, user-friendly messages\n- Race conditions and concurrency issues\n- Type safety violations\n\n### Architecture (cross-reference with OrgMemory)\n- Does this follow existing patterns?\n- Are new abstractions consistent with the codebase?\n- Is there unnecessary coupling?\n- Are there violations of established decisions?\n\n### Testing\n- Coverage of new code paths (happy path, error path, edge cases)\n- Test quality (meaningful assertions, not just coverage metrics)\n- Integration test coverage for API changes\n- Are mocking practices appropriate?\n\n### Maintainability\n- Clear naming and documentation\n- Complexity hotspots (cyclomatic complexity, deep nesting)\n- TODO\u002FFIXME comments that should be resolved\n- Breaking changes properly flagged\n\n## Output Format:\nGenerate a review in this structure:\n\n### Summary\nBrief overview of the changes and overall assessment.\n\n### Critical Issues (must fix before merge)\n- [ ] Issue 1: \u003Cdescription> (file:line)\n- [ ] Issue 2: \u003Cdescription> (file:line)\n\n### Warnings (should fix)\n- [ ] Warning 1: \u003Cdescription> (file:line)\n\n### Suggestions (nice to have)\n- Suggestion 1: \u003Cdescription>\n\n### OrgMemory Alignment\n- ✅ Aligned: \u003Cdecision\u002Fpattern followed>\n- ⚠️ Deviation: \u003Cdecision not followed, with justification if valid>\"\n```\n\n### 4. Post Review\n\nBased on findings:\n\n```bash\n# If no critical issues:\ngh pr review $PR_NUMBER --approve \\\n  --body \"## Automated Review by Claude Code + Nuvel OrgMemory\n\n$(cat review-output.md)\n\nReviewed against OrgMemory standards and project conventions.\"\n\n# If issues found:\ngh pr review $PR_NUMBER --request-changes \\\n  --body \"$(cat review-output.md)\"\n\n# For comments only:\ngh pr review $PR_NUMBER --comment \\\n  --body \"$(cat review-output.md)\"\n```\n\n### 5. Post-Review Actions\n\n```bash\n# If new patterns or anti-patterns were found:\nclaude -p \"Update nuvel-orgmemory with review insights from PR #${PR_NUMBER}: \\\n  - Any new patterns that should be documented \\\n  - Anti-patterns to avoid in future \\\n  - Updated component documentation if architecture changed\"\n```\n\n## Review Severity Guidelines\n\n| Severity | Criteria | Action |\n|----------|----------|--------|\n| Critical | Security vulnerability, data loss risk, breaks existing functionality | Request changes, block merge |\n| Warning | Performance regression, missing error handling, test gap | Request changes or comment |\n| Suggestion | Code style, naming, minor optimizations | Comment, non-blocking |\n\n## Pitfalls\n- **Review scope creep**: Focus review on the PR's stated purpose. Avoid suggesting unrelated refactors.\n- **OrgMemory staleness**: If team practices evolved but OrgMemory is outdated, note the discrepancy rather than blocking on it.\n- **Large PRs**: For PRs over 400 lines, request the author to split or focus review on the most critical files.\n- **False confidence**: Claude Code may miss subtle bugs. Critical PRs should always have human review in addition to automated review.\n\n## Verification\n1. Review posted on the PR: `gh pr view $PR_NUMBER --comments`\n2. All critical issues have corresponding comments\n3. Review references specific OrgMemory decisions\u002Fpatterns\n4. Post-review OrgMemory update completed (if applicable)",{"name":5,"description":7},"main","41d246dd855999c6bc4be528bc8d0d1b10ac8c47","plugins\u002Fclaude-code-plugin\u002Fskills\u002Fcc-review",1,"https:\u002F\u002Fgithub.com\u002FFolken2\u002Fnuvel","https:\u002F\u002Ffolken2.github.io\u002Fnuvel\u002F","https:\u002F\u002Fgithub.com\u002FFolken2","folch.ai","2026-11-05 22:40:38",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add Folken2\u002Fnuvel --skill cc-review",{"tool":56,"command":57},"bunx","bunx skills add Folken2\u002Fnuvel --skill cc-review",{"tool":59,"command":60},"pnpm","pnpm dlx skills add Folken2\u002Fnuvel --skill cc-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FFolken2\u002Fnuvel\u002Fblob\u002Fmain\u002Fplugins\u002Fclaude-code-plugin\u002Fskills\u002Fcc-review\u002FSKILL.md",true,[],[65,74,91,118,134,150],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":36},"01M6KVZNJQ7AVMVBS205404CS7","greet","Greet a user warmly by name.","https:\u002F\u002Fgithub.com\u002FFolken2\u002Fnuvel\u002Fblob\u002Fmain\u002Ftests\u002Ftest_agent_plugins\u002Ffixtures\u002Fvalid-full\u002Fskills\u002Fgreet\u002FSKILL.md",[],[67,72,73],"user","name",{"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":85,"publishedAt":36},"01M6KVZHYK2C9S5GRM3PZAFDXG","hello","A simple hello skill that survives a broken mcp.json.","https:\u002F\u002Fgithub.com\u002FFolken2\u002Fnuvel\u002Fblob\u002Fmain\u002Ftests\u002Ftest_agent_plugins\u002Ffixtures\u002Fbad-mcp\u002Fskills\u002Fhello\u002FSKILL.md",[80],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[76,86,87,88,89,90],"MCP","hello skill","json","broken","simple",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":106,"publishedAt":36},"01M6KVZC94REQZ852EJ99ZXATK","grok-workflows","Prompt templates and workflows for using xAI GrokBot with Nuvel — code, design, research, and automated pipelines.","https:\u002F\u002Fgithub.com\u002FFolken2\u002Fnuvel\u002Fblob\u002Fmain\u002Fplugins\u002Fgrokbot-plugin\u002Fskills\u002Fgrok-workflows\u002FSKILL.md",[97,100,101],{"categoryNo":98,"categoryName":99,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[107,108,109,110,111,112,113,33,114,115,116,117,26,24,23],"workflows","grok","grok workflows","design","research","prompt","prompt templates","templates","xai","grokbot","pipelines",{"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":36},"01M6KVZ7BA5MJ1N614MTP2JXCQ","grok-setup","Configure xAI GrokBot with Nuvel API integration and project context for Nuvel-aligned development.","https:\u002F\u002Fgithub.com\u002FFolken2\u002Fnuvel\u002Fblob\u002Fmain\u002Fplugins\u002Fgrokbot-plugin\u002Fskills\u002Fgrok-setup\u002FSKILL.md",[],[108,125,126,24,26,127,23,128,129,130,116,131,132,133,115,30],"grok setup","setup","project","project context","api integration","configure","development","integration","api",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":141,"publishedAt":36},"01M6KVZ3WYQ6V6XVCRE77WT2WY","cursor-setup","Configure Cursor IDE with Nuvel rules, MCP server integration, and project settings for OrgMemory-aware development.","https:\u002F\u002Fgithub.com\u002FFolken2\u002Fnuvel\u002Fblob\u002Fmain\u002Fplugins\u002Fcursor-plugin\u002Fskills\u002Fcursor-setup\u002FSKILL.md",[140],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},[142,143,126,132,86,144,131,145,146,130,147,148,127,26,24,149,23],"cursor","cursor setup","mcp server","server","ide","Rules","settings","project settings",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":36},"01M6KVZ0GGSJM4AC8PK7G53H85","cursor-review","Use Cursor IDE with Nuvel OrgMemory to review changes — diff analysis, standards checking, and pre-commit review.","https:\u002F\u002Fgithub.com\u002FFolken2\u002Fnuvel\u002Fblob\u002Fmain\u002Fplugins\u002Fcursor-plugin\u002Fskills\u002Fcursor-review\u002FSKILL.md",[],[157,142,21,158,159,160,161,146,29,162,22,26,163,164,23],"cursor review","commit","review changes","pre-commit","analysis","diff","changes","diff analysis"]