coderabbit-core-workflow-a
Execute CodeRabbit primary workflow: automated PR code review with configuration. Use when setting up automated code reviews on pull requests, configuring review behavior, or establishing the core CodeRabbit review loop. Trigger with phrases like "coderabbit review workflow", "coderabbit PR review", "coderabbit auto review", "configure coderabbit reviews".
What this skill does
# CodeRabbit Core Workflow A: Automated PR Review
## Overview
The primary CodeRabbit workflow: a developer opens a PR, CodeRabbit automatically analyzes the diff, posts a walkthrough summary and line-level comments, and the developer addresses feedback. This skill covers configuration, review profiles, path instructions, and the full review lifecycle.
## Prerequisites
- CodeRabbit GitHub App installed (see `coderabbit-install-auth`)
- `.coderabbit.yaml` in repository root
- At least one PR-capable branch
## Instructions
### Step 1: Configure the Review Pipeline
```yaml
# .coderabbit.yaml - Production-ready configuration
language: "en-US"
early_access: false
reviews:
profile: "assertive" # chill = less feedback, assertive = more thorough
request_changes_workflow: true # CodeRabbit marks review as "changes requested" for issues
high_level_summary: true # Post a walkthrough comment summarizing all changes
high_level_summary_in_walkthrough: true
review_status: true # Show review progress status
collapse_walkthrough: false # Keep walkthrough expanded
sequence_diagrams: true # Generate control flow diagrams
poem: false # Disable poems in review summary
auto_review:
enabled: true
drafts: false # Skip draft PRs
base_branches:
- main
- develop
ignore_title_keywords:
- "WIP"
- "DO NOT MERGE"
- "chore: bump"
path_filters:
- "!**/*.lock"
- "!**/*.snap"
- "!**/generated/**"
- "!dist/**"
- "!**/*.min.js"
- "!vendor/**"
path_instructions:
- path: "src/api/**"
instructions: |
Review for: input validation, proper HTTP status codes, auth middleware usage,
error response format per RFC 7807. Flag missing error handling.
- path: "src/db/**"
instructions: |
Review for: parameterized queries (no string concatenation), transaction boundaries,
proper connection cleanup, index usage. Flag N+1 query patterns.
- path: "**/*.test.*"
instructions: |
Review for: assertion completeness, edge case coverage, proper async handling.
Do NOT comment on test naming conventions or import order.
- path: ".github/workflows/**"
instructions: |
Review for: pinned action versions (use SHA not tag), no secrets in logs,
timeout-minutes on all jobs, OIDC for cloud auth.
chat:
auto_reply: true
# Finishing touches configuration
reviews:
finishing_touches:
docstrings:
enabled: true # Allow @coderabbitai generate-docstrings command
```
### Step 2: Understand the Review Lifecycle
```
Developer opens/updates PR
│
▼
┌─────────────────────────────────┐
│ CodeRabbit analyzes diff │
│ (typically 2-5 min, up to 15 │
│ min for 1000+ line PRs) │
└─────────┬───────────────────────┘
│
├──▶ Walkthrough comment (summary + sequence diagram)
│
├──▶ Line-level comments (bugs, suggestions, improvements)
│
└──▶ Review state (approved / changes_requested)
│
▼
Developer addresses feedback
│
┌─────────┴──────────┐
│ │
Reply to comment Push new commits
(conversation) (incremental re-review)
│ │
▼ ▼
CodeRabbit responds CodeRabbit reviews
with explanation only changed files
```
### Step 3: Interact with Reviews
```markdown
# In any PR comment:
@coderabbitai full review # Re-review all files from scratch
@coderabbitai summary # Regenerate walkthrough summary
@coderabbitai resolve # Mark all CodeRabbit comments as resolved
@coderabbitai generate-docstrings # Auto-generate docstrings for functions
@coderabbitai configuration # Show current active config as YAML
@coderabbitai help # List all commands
# Reply to any CodeRabbit inline comment to discuss the feedback.
# CodeRabbit maintains conversation context and will explain its reasoning.
# In PR description, add instructions for this specific review:
# "Focus on security implications of the auth changes"
```
### Step 4: Configure Finishing Touch Recipes
```yaml
# .coderabbit.yaml - Custom finishing touch recipes (open beta)
finishing_touches:
recipes:
- name: "fix-imports"
description: "Sort and organize imports"
instructions: |
Sort all imports alphabetically. Group: external packages first,
then internal modules, then relative imports. Remove unused imports.
- name: "tighten-types"
description: "Replace any with specific types"
instructions: |
Replace all `any` types with proper TypeScript types.
Use `unknown` for truly unknown values. Add type guards where needed.
```
```markdown
# Trigger recipes in a PR comment:
@coderabbitai run fix-imports
@coderabbitai run tighten-types
# Or check the boxes in the Finishing Touches section of the walkthrough
```
## Output
- Automated review on every PR targeting configured branches
- Walkthrough summary with sequence diagrams
- Line-level feedback categorized by severity
- Interactive conversation on review comments
- Finishing touch recipes for automated code improvements
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| Review takes 15+ minutes | PR has 1000+ changed lines | Split into smaller PRs |
| No review posted | PR targets non-configured branch | Add branch to `base_branches` |
| Reviews on generated files | Missing path_filters | Add `!**/generated/**` to path_filters |
| Too many nitpick comments | Profile set to assertive | Switch to `chill` for experienced teams |
| Config changes not applied | YAML syntax error | Run `@coderabbitai configuration` to verify |
| Review on draft PR | `drafts: true` in config | Set `drafts: false` to skip drafts |
## Resources
- [Configuration Reference](https://docs.coderabbit.ai/reference/configuration)
- [Review Commands](https://docs.coderabbit.ai/reference/review-commands)
- [Finishing Touches](https://docs.coderabbit.ai/finishing-touches/index)
## Next Steps
For configuration tuning and noise reduction, see `coderabbit-core-workflow-b`.
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.