CodeRabbit Reviewer
Processes CodeRabbit automated review feedback and helps address issues. Assumes CodeRabbit is already installed on the repository.
Prerequisites
- PR created and pushed to GitHub
- CodeRabbit installed on Comfy-Org/ComfyUI_frontend (it is)
Workflow
1. Verify PR Exists
PR_NUMBER=$(gh pr view --json number -q '.number')
echo "PR #$PR_NUMBER"
2. Wait for CodeRabbit Review
CodeRabbit reviews automatically on PR creation. Check for review comment:
# Check for CodeRabbit review comment
gh pr view $PR_NUMBER --json comments --jq '.comments[] | select(.author.login == "coderabbitai")'
Typical wait time: 2-5 minutes for small PRs.
To manually trigger a re-review:
gh pr comment $PR_NUMBER --body "@coderabbitai review"
3. Parse Review Feedback
Extract actionable items from CodeRabbit's review:
## CodeRabbit Review Summary
### Critical Issues
- [ ] {file:line} - {issue description}
### Suggestions
- [ ] {file:line} - {suggestion}
### Nitpicks
- [ ] {file:line} - {minor improvement}
4. Categorize by Severity
| Category | Action Required | Auto-fixable |
|---|---|---|
| Critical | Must fix before merge | Sometimes |
| Suggestion | Should consider | Often |
| Nitpick | Nice to have | Usually |
5. Present to User
CodeRabbit Review Complete
## Summary
- Critical: 2 issues
- Suggestions: 5 items
- Nitpicks: 3 items
## Critical Issues (must fix)
1. src/components/Feature.vue:45 - Potential null reference
2. src/stores/data.ts:23 - Missing error handling
Options:
1. Auto-fix critical issues
2. Show all feedback details
3. Dismiss and proceed to human review
Your choice:
6. Fix Issues
For fixable issues, apply changes directly or dispatch subagents:
Fix CodeRabbit critical issue:
File: {file}
Line: {line}
Issue: {description}
Suggestion: {CodeRabbit's suggestion}
Apply fix and verify with `pnpm typecheck`.
7. Request Re-Review
After fixes:
git add -A
git commit -m "fix: address CodeRabbit review feedback"
git push
# Request re-review
gh pr comment $PR_NUMBER --body "@coderabbitai review"
CodeRabbit Commands
Trigger via PR comments:
| Command | Purpose |
|---|---|
@coderabbitai review | Full review |
@coderabbitai summary | Generate PR summary |
@coderabbitai resolve | Mark threads resolved |
Integration with Pipeline
Before: pr-creator (PR exists) After: review-orchestrator (human review)
Recommended flow:
- PR created → CodeRabbit auto-reviews
- Fix critical issues
- Human review with CodeRabbit context
- Merge
Configuration
Uses the production API by default. No configuration needed for read operations.
Defaults (no setup required):
- API URL:
https://api-gateway-856475788601.us-central1.run.app - Read-only endpoints at
/public/*require no authentication
For write operations (state transitions), set:
export PIPELINE_API_KEY="..." # Get from GCP Secret Manager or ask admin
API Integration
Fetch ticket context via the Pipeline API:
import { PipelineClient } from '@pipeline/client'
const client = new PipelineClient({
apiUrl: process.env.PIPELINE_API_URL || 'https://api-gateway-856475788601.us-central1.run.app',
agentId: process.env.AGENT_ID,
})
// Verify ticket exists - fail loudly if ticket-intake wasn't run
const ticket = await client.getTicket(ticketId).catch(() => null)
if (!ticket) {
console.error('❌ No pipeline ticket found. Run ticket-intake first to register this ticket.')
// Stop here - ticket-intake must run before this skill
}
// Use ticket.prNumber if available
What Stays Local
- CodeRabbit review parsing and categorization
- Fix dispatching and application
- PR comment interactions via
ghCLI
