[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74TD2XPMQPBDQC5W1NETQ6K":3,"skill-same:01M74TD2XPMQPBDQC5W1NETQ6K":49},{"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":29,"commitSha":30,"skillDirectory":5,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M74TD2XPMQPBDQC5W1NETQ6K","coderabbit-reference-architecture",null,"Implement CodeRabbit reference architecture with best-practice project layout.\nUse when designing new CodeRabbit integrations, reviewing project structure,\nor establishing architecture standards for CodeRabbit applications.\nTrigger with phrases like \"coderabbit architecture\", \"coderabbit best practices\",\n\"coderabbit project structure\", \"how to organize coderabbit\", \"coderabbit layout\".","SamuelChien\u002Fmega-skills-collection","SamuelChien","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4652114?v=4","01M74KK34WVHA0P5ZYSJRDDFMG","Samuel Chien","01M74KK35FQN1N9VZ9EPTH3P2S",0,"MIT","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fcoderabbit-reference-architecture\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: coderabbit-reference-architecture\ndescription: |\n  Implement CodeRabbit reference architecture with best-practice project layout.\n  Use when designing new CodeRabbit integrations, reviewing project structure,\n  or establishing architecture standards for CodeRabbit applications.\n  Trigger with phrases like \"coderabbit architecture\", \"coderabbit best practices\",\n  \"coderabbit project structure\", \"how to organize coderabbit\", \"coderabbit layout\".\nallowed-tools: Read, Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\n---\n# CodeRabbit Reference Architecture\n\n## Overview\nConfigure CodeRabbit AI code review for team workflows. Covers repository configuration, custom review instructions, path-based rules, and integration with CI pipelines for automated review enforcement.\n\n## Prerequisites\n- CodeRabbit GitHub\u002FGitLab app installed\n- Repository admin access for configuration\n- Understanding of team coding standards\n- CI pipeline for review status checks\n\n## Architecture Diagram\n\n```\n┌──────────────┐     ┌──────────────┐     ┌──────────────┐\n│  Developer   │────▶│  Pull        │────▶│  CodeRabbit  │\n│  Push\u002FPR     │     │  Request     │     │  AI Review   │\n└──────────────┘     └──────────────┘     └──────┬───────┘\n                                                  │\n                     ┌────────────────────────────┤\n                     │                            │\n                     ▼                            ▼\n              ┌──────────────┐          ┌──────────────┐\n              │ Line-level   │          │ Summary      │\n              │ Comments     │          │ Review       │\n              └──────┬───────┘          └──────┬───────┘\n                     │                          │\n                     ▼                          ▼\n              ┌──────────────┐          ┌──────────────┐\n              │ Developer    │          │ CI Status    │\n              │ Response     │          │ Check        │\n              └──────────────┘          └──────────────┘\n```\n\n## Instructions\n\n### Step 1: Create Repository Configuration\n```yaml\n# .coderabbit.yaml - Root configuration\nlanguage: \"en-US\"\nearly_access: false\n\nreviews:\n  profile: \"assertive\"        # Options: chill, assertive, proactive\n  request_changes_workflow: true\n  high_level_summary: true\n  poem: false\n  review_status: true\n  collapse_walkthrough: false\n  path_instructions:\n    - path: \"src\u002Fapi\u002F**\"\n      instructions: |\n        Review for REST API best practices:\n        - Validate all inputs with zod schemas\n        - Return proper HTTP status codes\n        - Include error response bodies per RFC 7807  # 7807 = configured value\n        - Check for SQL injection in query parameters\n    - path: \"src\u002Fcomponents\u002F**\"\n      instructions: |\n        Review React components for:\n        - Proper use of hooks (no conditional hooks)\n        - Memoization where appropriate\n        - Accessibility (aria labels, keyboard navigation)\n        - Component size (flag if >200 lines)  # HTTP 200 OK\n    - path: \"**\u002F*.test.*\"\n      instructions: |\n        Review tests for:\n        - Meaningful test descriptions\n        - Edge cases covered\n        - No implementation details tested\n        - Proper async handling\n\n  auto_review:\n    enabled: true\n    drafts: false\n    base_branches:\n      - \"main\"\n      - \"develop\"\n    ignore_title_keywords:\n      - \"WIP\"\n      - \"DO NOT MERGE\"\n\nchat:\n  auto_reply: true\n```\n\n### Step 2: Configure Path-Based Review Rules\n```yaml\n# .coderabbit.yaml continued\nreviews:\n  path_filters:\n    # Skip auto-generated files\n    - \"!**\u002F*.generated.ts\"\n    - \"!**\u002Fgenerated\u002F**\"\n    - \"!package-lock.json\"\n    - \"!pnpm-lock.yaml\"\n    - \"!**\u002F*.min.js\"\n    - \"!dist\u002F**\"\n\n    # Always review security-sensitive paths\n    - \"+src\u002Fauth\u002F**\"\n    - \"+src\u002Fmiddleware\u002F**\"\n    - \"+**\u002Fmigrations\u002F**\"\n\n  tools:\n    eslint:\n      enabled: true\n    biome:\n      enabled: true\n    shellcheck:\n      enabled: true\n    markdownlint:\n      enabled: true\n```\n\n### Step 3: Custom Review Instructions for Team Standards\n```yaml\n# .coderabbit.yaml - Team-specific instructions\nreviews:\n  path_instructions:\n    - path: \"**\"\n      instructions: |\n        Team coding standards:\n        1. All exported functions must have JSDoc comments\n        2. Use named exports, never default exports\n        3. Prefer const assertions for literal types\n        4. Error handling: never catch and ignore silently\n        5. Logging: use structured logger, never console.log in production\n\n    - path: \"src\u002Fdb\u002F**\"\n      instructions: |\n        Database layer rules:\n        - All queries must use parameterized statements\n        - Include index hints for complex queries\n        - Transactions required for multi-table mutations\n        - Migration files must be reversible\n\n    - path: \".github\u002Fworkflows\u002F**\"\n      instructions: |\n        CI\u002FCD pipeline rules:\n        - Pin all action versions to SHA, not tags\n        - Never use secrets in step names or logs\n        - Include timeout-minutes on all jobs\n        - Use OIDC for cloud provider auth\n```\n\n### Step 4: Integrate with CI Pipeline\n```yaml\n# .github\u002Fworkflows\u002Fpr-checks.yml\nname: PR Checks\n\non:\n  pull_request:\n    types: [opened, synchronize, reopened]\n\njobs:\n  wait-for-coderabbit:\n    runs-on: ubuntu-latest\n    steps:\n      - name: Wait for CodeRabbit review\n        uses: actions\u002Fgithub-script@v7\n        with:\n          script: |\n            \u002F\u002F Check if CodeRabbit has reviewed\n            const reviews = await github.rest.pulls.listReviews({\n              owner: context.repo.owner,\n              repo: context.repo.repo,\n              pull_number: context.issue.number,\n            });\n\n            const coderabbitReview = reviews.data.find(\n              r => r.user.login === 'coderabbitai[bot]'\n            );\n\n            if (!coderabbitReview) {\n              core.info('Waiting for CodeRabbit review...');\n            }\n```\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Review not triggered | PR to non-configured branch | Add branch to `base_branches` |\n| Too many comments | Profile too aggressive | Switch to `chill` profile |\n| Ignoring config changes | YAML syntax error | Validate YAML before committing |\n| Reviewing generated files | Missing path filter | Add `!` exclusion patterns |\n\n## Examples\n\n### Minimal Configuration\n```yaml\n# .coderabbit.yaml - Quick start\nreviews:\n  profile: \"assertive\"\n  auto_review:\n    enabled: true\n    drafts: false\n```\n\n## Resources\n- [CodeRabbit Configuration](https:\u002F\u002Fdocs.coderabbit.ai\u002Fconfiguration)\n- [CodeRabbit Path Instructions](https:\u002F\u002Fdocs.coderabbit.ai\u002Fguides\u002Freview-instructions)\n- [CodeRabbit Tools](https:\u002F\u002Fdocs.coderabbit.ai\u002Ftools)\n\n## Output\n\n- Configuration files or code changes applied to the project\n- Validation report confirming correct implementation\n- Summary of changes made and their rationale","# CodeRabbit Reference Architecture\n\n## Overview\nConfigure CodeRabbit AI code review for team workflows. Covers repository configuration, custom review instructions, path-based rules, and integration with CI pipelines for automated review enforcement.\n\n## Prerequisites\n- CodeRabbit GitHub\u002FGitLab app installed\n- Repository admin access for configuration\n- Understanding of team coding standards\n- CI pipeline for review status checks\n\n## Architecture Diagram\n\n```\n┌──────────────┐     ┌──────────────┐     ┌──────────────┐\n│  Developer   │────▶│  Pull        │────▶│  CodeRabbit  │\n│  Push\u002FPR     │     │  Request     │     │  AI Review   │\n└──────────────┘     └──────────────┘     └──────┬───────┘\n                                                  │\n                     ┌────────────────────────────┤\n                     │                            │\n                     ▼                            ▼\n              ┌──────────────┐          ┌──────────────┐\n              │ Line-level   │          │ Summary      │\n              │ Comments     │          │ Review       │\n              └──────┬───────┘          └──────┬───────┘\n                     │                          │\n                     ▼                          ▼\n              ┌──────────────┐          ┌──────────────┐\n              │ Developer    │          │ CI Status    │\n              │ Response     │          │ Check        │\n              └──────────────┘          └──────────────┘\n```\n\n## Instructions\n\n### Step 1: Create Repository Configuration\n```yaml\n# .coderabbit.yaml - Root configuration\nlanguage: \"en-US\"\nearly_access: false\n\nreviews:\n  profile: \"assertive\"        # Options: chill, assertive, proactive\n  request_changes_workflow: true\n  high_level_summary: true\n  poem: false\n  review_status: true\n  collapse_walkthrough: false\n  path_instructions:\n    - path: \"src\u002Fapi\u002F**\"\n      instructions: |\n        Review for REST API best practices:\n        - Validate all inputs with zod schemas\n        - Return proper HTTP status codes\n        - Include error response bodies per RFC 7807  # 7807 = configured value\n        - Check for SQL injection in query parameters\n    - path: \"src\u002Fcomponents\u002F**\"\n      instructions: |\n        Review React components for:\n        - Proper use of hooks (no conditional hooks)\n        - Memoization where appropriate\n        - Accessibility (aria labels, keyboard navigation)\n        - Component size (flag if >200 lines)  # HTTP 200 OK\n    - path: \"**\u002F*.test.*\"\n      instructions: |\n        Review tests for:\n        - Meaningful test descriptions\n        - Edge cases covered\n        - No implementation details tested\n        - Proper async handling\n\n  auto_review:\n    enabled: true\n    drafts: false\n    base_branches:\n      - \"main\"\n      - \"develop\"\n    ignore_title_keywords:\n      - \"WIP\"\n      - \"DO NOT MERGE\"\n\nchat:\n  auto_reply: true\n```\n\n### Step 2: Configure Path-Based Review Rules\n```yaml\n# .coderabbit.yaml continued\nreviews:\n  path_filters:\n    # Skip auto-generated files\n    - \"!**\u002F*.generated.ts\"\n    - \"!**\u002Fgenerated\u002F**\"\n    - \"!package-lock.json\"\n    - \"!pnpm-lock.yaml\"\n    - \"!**\u002F*.min.js\"\n    - \"!dist\u002F**\"\n\n    # Always review security-sensitive paths\n    - \"+src\u002Fauth\u002F**\"\n    - \"+src\u002Fmiddleware\u002F**\"\n    - \"+**\u002Fmigrations\u002F**\"\n\n  tools:\n    eslint:\n      enabled: true\n    biome:\n      enabled: true\n    shellcheck:\n      enabled: true\n    markdownlint:\n      enabled: true\n```\n\n### Step 3: Custom Review Instructions for Team Standards\n```yaml\n# .coderabbit.yaml - Team-specific instructions\nreviews:\n  path_instructions:\n    - path: \"**\"\n      instructions: |\n        Team coding standards:\n        1. All exported functions must have JSDoc comments\n        2. Use named exports, never default exports\n        3. Prefer const assertions for literal types\n        4. Error handling: never catch and ignore silently\n        5. Logging: use structured logger, never console.log in production\n\n    - path: \"src\u002Fdb\u002F**\"\n      instructions: |\n        Database layer rules:\n        - All queries must use parameterized statements\n        - Include index hints for complex queries\n        - Transactions required for multi-table mutations\n        - Migration files must be reversible\n\n    - path: \".github\u002Fworkflows\u002F**\"\n      instructions: |\n        CI\u002FCD pipeline rules:\n        - Pin all action versions to SHA, not tags\n        - Never use secrets in step names or logs\n        - Include timeout-minutes on all jobs\n        - Use OIDC for cloud provider auth\n```\n\n### Step 4: Integrate with CI Pipeline\n```yaml\n# .github\u002Fworkflows\u002Fpr-checks.yml\nname: PR Checks\n\non:\n  pull_request:\n    types: [opened, synchronize, reopened]\n\njobs:\n  wait-for-coderabbit:\n    runs-on: ubuntu-latest\n    steps:\n      - name: Wait for CodeRabbit review\n        uses: actions\u002Fgithub-script@v7\n        with:\n          script: |\n            \u002F\u002F Check if CodeRabbit has reviewed\n            const reviews = await github.rest.pulls.listReviews({\n              owner: context.repo.owner,\n              repo: context.repo.repo,\n              pull_number: context.issue.number,\n            });\n\n            const coderabbitReview = reviews.data.find(\n              r => r.user.login === 'coderabbitai[bot]'\n            );\n\n            if (!coderabbitReview) {\n              core.info('Waiting for CodeRabbit review...');\n            }\n```\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Review not triggered | PR to non-configured branch | Add branch to `base_branches` |\n| Too many comments | Profile too aggressive | Switch to `chill` profile |\n| Ignoring config changes | YAML syntax error | Validate YAML before committing |\n| Reviewing generated files | Missing path filter | Add `!` exclusion patterns |\n\n## Examples\n\n### Minimal Configuration\n```yaml\n# .coderabbit.yaml - Quick start\nreviews:\n  profile: \"assertive\"\n  auto_review:\n    enabled: true\n    drafts: false\n```\n\n## Resources\n- [CodeRabbit Configuration](https:\u002F\u002Fdocs.coderabbit.ai\u002Fconfiguration)\n- [CodeRabbit Path Instructions](https:\u002F\u002Fdocs.coderabbit.ai\u002Fguides\u002Freview-instructions)\n- [CodeRabbit Tools](https:\u002F\u002Fdocs.coderabbit.ai\u002Ftools)\n\n## Output\n\n- Configuration files or code changes applied to the project\n- Validation report confirming correct implementation\n- Summary of changes made and their rationale",{"name":5,"author":24,"license":15,"version":25,"description":26,"allowed-tools":27,"compatible-with":28},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Implement CodeRabbit reference architecture with best-practice project layout.\nUse when designing new CodeRabbit integrations, reviewing project structure,\nor establishing architecture standards for CodeRabbit applications.\nTrigger with phrases like \"coderabbit architecture\", \"coderabbit best practices\",\n\"coderabbit project structure\", \"how to organize coderabbit\", \"coderabbit layout\".\n","Read, Grep","claude-code, codex, openclaw","main","c2b1fdccc779e99ac814e55fb69ca8d71215dd0f","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection","https:\u002F\u002Fgithub.com\u002FSamuelChien","http:\u002F\u002Fsamuelchien.com\u002F","2026-05-26 08:27:14",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add SamuelChien\u002Fmega-skills-collection --skill coderabbit-reference-architecture",{"tool":41,"command":42},"bunx","bunx skills add SamuelChien\u002Fmega-skills-collection --skill coderabbit-reference-architecture",{"tool":44,"command":45},"pnpm","pnpm dlx skills add SamuelChien\u002Fmega-skills-collection --skill coderabbit-reference-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fcoderabbit-reference-architecture\u002FSKILL.md",true,[],[50,57,64,71,78,86],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M76R4WZQZAXGGXMQCA0FZ716","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"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},"01M76R4T9KENDH7FENGZQHBW4G","zustand-store-creator","Zustand Store Creator - Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M76R3YWN84B7SANJ52X799ZE","zero-trust-config-helper","Zero Trust Config Helper - Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M76R3HNSV2AEYSKHM915GJ58","zapier-integration-helper","Zapier Integration Helper - Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M76R3DJSKAT4FA7DV4BF3GCE","zai-cli","Execute z.AI CLI providing vision, search, reader, and GitHub exploration via CLI and MCP.\nUse when user needs image\u002Fvideo analysis, OCR, UI-to-code conversion, error diagnosis,\nreal-time web search, web page to markdown extraction, or GitHub code exploration.\nTrigger with phrases like \"analyze this image\", \"search the web for\", \"read this page\",\n\"explore this repo\", or \"use zai\". Requires Z_AI_API_KEY.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzai-cli\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M76R2KAM699XE9AJVAWE4H2E","yt-research","Research competitor YouTube channels, niches, and trending topics for your content strategy.\nUse this skill whenever the user says \"research channels\", \"analyze competitors\", \"find trending topics\",\n\"niche analysis\", \"competitive research\", \"what are other creators doing\", \"scrape YouTube channels\",\nor wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fyt-research\u002FSKILL.md",[],[]]