菜单
Use when working with CodeRabbit AI code review. Covers triggering reviews, interpreting feedback, addressing comments, and PR workflow integration.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | coderabbit |
| description | Use when working with CodeRabbit AI code review. Covers triggering reviews, interpreting feedback, addressing comments, and PR workflow integration. |
CodeRabbit provides AI-powered code review for pull requests. This skill covers how to trigger reviews, interpret feedback, and address comments effectively.
| Action | Command/Method |
|---|---|
| Trigger review | Auto on PR, or @coderabbitai review |
| Full review | @coderabbitai full review |
| Specific files | @coderabbitai review src/auth/* |
| Ignore file | @coderabbitai ignore on comment |
| Summary | @coderabbitai summary |
CodeRabbit reviews PRs automatically when:
# Full review of entire PR
@coderabbitai full review
# Review specific files
@coderabbitai review src/components/Button.tsx
# Review specific paths
@coderabbitai review src/auth/*
# Get summary only
@coderabbitai summary
# Generate PR description
@coderabbitai generate description
| Type | Meaning | Action Required |
|---|---|---|
| Bug | Potential runtime error | Fix immediately |
| Security | Security vulnerability | Fix immediately |
| Performance | Inefficient code | Evaluate and fix |
| Best Practice | Code quality suggestion | Consider applying |
| Style | Formatting/convention | Apply if team standard |
| Nitpick | Minor suggestion | Optional |
1. Read CodeRabbit comment
2. Determine action:
- Fix: Make code change, push commit
- Explain: Reply with reasoning
- Disagree: Reply with justification
- Ignore: Mark as resolved with reason
3. Reply to comment:
- "Fixed in abc123"
- "Intentional because [reason]"
- "Won't fix: [justification]"
4. Resolve conversation when addressed
Fixed:
Fixed in [commit hash]. Added validation as suggested.
Intentional:
Intentional - this pattern is used for [reason].
See [link to docs/discussion] for context.
Won't Fix:
Acknowledged, but won't fix because:
- [reason 1]
- [reason 2]
Marking as resolved.
Need Clarification:
@coderabbitai Can you clarify? I don't understand how [X] applies here.
# Pause reviews on this PR
@coderabbitai pause
# Resume reviews
@coderabbitai resume
# Ignore specific file in future reviews
@coderabbitai ignore path/to/file.ts
# Get help
@coderabbitai help
CodeRabbit is configured via .coderabbit.yaml:
reviews:
auto_review: true
path_instructions:
- path: "src/components/**"
instructions: "Focus on React best practices"
- path: "src/api/**"
instructions: "Check for proper error handling"
When CodeRabbit raises multiple similar issues:
# 1. List all comments
gh pr view --comments | grep -A5 "coderabbit"
# 2. Make bulk fix
# ... apply pattern fix across files ...
# 3. Single commit addressing all
git commit -m "fix: address CodeRabbit review feedback
- Add error handling to all API calls
- Fix type safety issues
- Update deprecated APIs"
# 4. Push and reply
git push
Thanks for the suggestion. I've considered this but will keep
the current approach because:
1. [Technical reason]
2. [Team convention]
3. [Performance consideration]
Happy to discuss further if you see issues I'm missing.
After CodeRabbit review:
Never:
Always:
Related skills: submit-pr, git-expert Pairs with: verification, tdd
Use when working with git operations including commits, branches, worktrees, and PRs. Covers the full git workflow from feature isolation to PR submission.
Complete PR submission pipeline with local sub-agent review before pushing, CI verification, and automated review integration. Always dispatches code-reviewer and code-simplifier for code changes, plus conditional reviewers (security, performance, dependency, accessibility, i18n, type-design, etc.) based on change type. Waits for CI with `gh pr checks --watch`. Integrates CodeRabbit and Greptile feedback.
GitHub CLI patterns for PR reviews, comments, and API operations. Use when working with gh api commands, especially for review threads and comments.
Use when following a written plan or task list. Checkpoint verification at each step. Triggers - execute plan, follow plan, implement plan, next step, continue, proceed.
Use for parallel branch development with workspace isolation.
Use when implementing analytics, event tracking, or setting up dashboards. Covers privacy-first tracking, event patterns, and common analytics tools.