- Home
- Skills
- Bitsoex
- Bitso Java
- Coderabbit Workflow
coderabbit-workflow_skill
- JavaScript
35
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill bitsoex/bitso-java --skill coderabbit-workflow- SKILL.md3.4 KB
Overview
This skill provides a systematic workflow for addressing CodeRabbit review comments across a local CLI, PR threads, and commit attribution. It bundles scripts, reference docs, and conventions so you can find, fix, commit, and respond to CodeRabbit feedback consistently. Use it to get early local feedback or to close out comments on an open pull request.
How this skill works
The workflow offers two review modes: run a local CLI review before pushing, or export and process PR thread comments after CodeRabbit reviews your PR. Scripts export comments to JSON, run local reviews, and batch-reply to threads once comments are marked fixed. All fix commits must include a required Co-authored-by line for CodeRabbit attribution.
When to use it
- Before pushing code to get early automated feedback with the local CLI
- When a PR has CodeRabbit review comments that need systematic addressing
- When tasked to “fix coderabbit issues” or “address coderabbit comments”
- To automate batch replies to PR threads after applying fixes
- When you need consistent commit message templates and co-author attribution
Best practices
- Run run-local-review.ts locally before opening or updating a PR to catch issues early
- Export PR comments and sort by severity (critical, major, minor) to prioritize work
- Update exported JSON status from 'pending' to 'fixed' before running the reply script
- Include the required Co-authored-by line in every fix commit to maintain attribution
- Follow commit message templates in the commit-formats reference for traceability
Example use cases
- Run the CLI to detect issues locally and iterate until the report is clean before pushing
- Export PR comments, apply fixes, then batch-reply to threads with reply-to-threads.ts to close out discussions
- Use export-comments.ts to create a checklist that your team can share and mark as fixed
- Automate replies for multiple PRs by updating their JSON exports and running the batch reply script
- Enforce co-author attribution automatically by using the commit message templates from the references
FAQ
Set each comment's status from 'pending' to 'fixed' for items you addressed; the reply script only processes comments where status !== 'pending'.
How do I include CodeRabbit as a co-author on fix commits?
Add the required Co-authored-by line exactly as specified: Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>. Commit templates in the references show examples.