Menu
Systematic workflow for CodeRabbit reviews - local CLI, PR threads, and commit attribution
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
RFC-39 compliant API best practices for Java services. Covers request/response patterns, error handling, pagination, versioning, and authentication standards. Use when designing or reviewing REST APIs in Java services.
RFC-29 compliant changelog management with Common Changelog format and Unreleased section extension. Validates changelog on commits, generates from git history, and ensures all merged PRs are documented. Use when setting up changelog workflows or retrofitting existing repositories.
Enforces consistent coding standards across the codebase including naming conventions, code organization, and documentation requirements. Use when writing new code, reviewing pull requests, or refactoring existing code.
Database integration patterns for Java services using jOOQ and Flyway. Covers code generation, read/write splitting, migration guidelines, and version compatibility. Use when setting up or maintaining PostgreSQL integration.
Version catalog strategy, dependency management, BOMs, and version constraints for Java/Gradle projects. Covers version centralization, never-downgrade policy, bundle patterns, resolution strategies, and compatibility matrices.
RFC-44 compliant distributed locking patterns for Java services. Covers PostgreSQL advisory locks and Redis-based locking, migration workflows, and common patterns. Use when implementing or migrating distributed locking mechanisms.
| name | coderabbit-workflow |
| description | Systematic workflow for CodeRabbit reviews - local CLI, PR threads, and commit attribution |
| compatibility | All repositories with CodeRabbit enabled |
| metadata | {"version":"2.0.0","category":"code-quality","tags":["code-review","coderabbit","quality"],"triggers":["before-push","on-demand"]} |
Address CodeRabbit review comments systematically. Workflows for local CLI usage, PR thread processing, and commit attribution.
📚 references/ - Detailed documentation
🔧 scripts/ - Automation scripts
| Mode | When | Reference |
|---|---|---|
| Local CLI | Before push, get early feedback | references/cli-integration.md |
| PR Threads | After CodeRabbit reviews your PR | references/workflow-examples.md |
node .claude/skills/coderabbit-workflow/scripts/export-comments.ts --pr <number>references/workflow-examples.mdstatus: 'fixed')node .claude/skills/coderabbit-workflow/scripts/reply-to-threads.ts --file .tmp/coderabbit-*.jsonNote: The reply script only processes comments with status !== 'pending'. After applying fixes, update the JSON file to change status from 'pending' to 'fixed' before running the reply script.
| Script | Purpose |
|---|---|
scripts/run-local-review.ts | Run CodeRabbit CLI and save findings |
scripts/export-comments.ts | Export PR comments to local JSON |
scripts/reply-to-threads.ts | Batch reply to threads after fixes |
scripts/monitor-approval.ts | Poll for approval, request review/approval automatically |
| Reference | Content |
|---|---|
references/setup.md | Installation, authentication, troubleshooting |
references/cli-integration.md | CLI commands and async workflow |
references/commit-formats.md | All commit message templates |
references/workflow-examples.md | Complete workflow examples |
All CodeRabbit fix commits must include:
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
See references/commit-formats.md for all templates.
Use the monitor script to automatically wait for and request CodeRabbit approval:
# Monitor PR and automatically request review/approval when appropriate
node scripts/monitor-approval.ts --pr <number>
# With custom poll interval (default: 60s)
node scripts/monitor-approval.ts --pr <number> --interval 30
# Dry-run mode (show what would be done)
node scripts/monitor-approval.ts --pr <number> --dry-run
The monitor script:
--interval)Timing requirements (automated by monitor script):
| Time Since Last Commit | Action |
|---|---|
| 0-15 minutes | Wait for CodeRabbit to review automatically |
| 15+ minutes (no review) | Request review: @coderabbitai review |
| 30+ minutes (no approval) | Request approval: @coderabbitai approve |
Manual commands (if not using monitor script):
# Check time of last commit
git log -1 --format='%ci'
# Request review (after 15 min with no activity)
gh pr comment <PR_NUMBER> --body "@coderabbitai review"
# Request approval (after 30 min with no approval)
gh pr comment <PR_NUMBER> --body "@coderabbitai approve"