coderabbit-review
CodeRabbit Review
This skill provides instructions on how to use CodeRabbit CLI for code reviews, and how to handle the feedback received.
Instructions
- Check authentication status with
coderabbit auth status. If not logged in, prompt the user to log in usingcoderabbit auth login. - Determine whether to review uncommitted or committed code changes based on the git status.
- Run the appropriate CodeRabbit command without sandbox:
- For uncommitted changes:
coderabbit --plain --type uncommitted - For committed changes:
coderabbit --plain --type committed
- For uncommitted changes:
- When receiving the message "Review Completed", it indicates the review process is finished.
- If there are no review comments from CodeRabbit, inform the user that no issues were found.
- If there are review comments, address the issues as follows:
- If the comment points out clear bugs, coding standard violations, security issues, or performance improvements, make the necessary changes immediately.
- If the comment is overly strict, involves trade-offs, or requires significant architectural changes, ask the user for a decision before making any changes.
- Report back to the user with a summary of the comments received from CodeRabbit and the actions taken for each comment.
Note
- CodeRabbit reviews can take 5+ minutes. Please wait.
- You should communicate to the user in Japanese.
More from uwe-schwarz/skills
github-pr-review-workflow
Complete workflow for handling GitHub PR reviews using gh pr-review extension
40upgrade-dependencies-pr
Update a JavaScript, TypeScript, or Python project's dependencies to the latest published versions, remove exact pinned JS semver specs when appropriate, convert stray JS `latest` tags back to explicit semver ranges, evaluate release impact against the codebase and official release notes, identify newly introduced features and enforcement changes, apply required small upgrade fixes, open GitHub issues for larger or optional follow-up work, and finish by creating a branch, commit, push, and PR. Use when asked to upgrade dependencies, refresh packages, unpin dependency versions, or ship an end-to-end dependency maintenance PR.
12documentation
Automated documentation generation and management. Use for creating, updating, and maintaining project documentation including README files, API docs, and inline code comments.
8example-skill
An example skill demonstrating the Agent Skills format. Use this as a template for creating your own skills.
8your-skill-name
A clear description of what this skill does and when to use it. This should be comprehensive so agents understand when to activate this skill.
8code-review
Comprehensive code review guidelines for ensuring code quality, security, and maintainability. Use when reviewing pull requests, refactoring code, or ensuring best practices.
8