Menu
Triage CodeRabbitAI review comments on current PR, fix legitimate issues, push, resolve threads
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
Use when a user needs architecture or product-design sparring on system design, runtime boundaries, config, deployment, operations, or implementation plans; ask one focused question at a time.
Use when ready to ship confirmed local changes through a draft PR: check dirty-worktree scope, create a branch, stage only intended paths, commit, push, open a PR, wait for CI, and fix red checks.
Use when creating or updating current-state project context documentation under docs/context/.
Use when reviewing local code changes before a PR: review my changes/code, check my work, security review, review before push; rank bugs, security, perf, and production risks.
Create a committed Markdown todo in ~/.create-todo from a todo, task, follow-up, $create-todo request, or current conversation context.
Use when creating concise Markdown docs-as-code for critical user journeys, flows, acceptance scenarios, service blueprints, telemetry, portfolios, story maps, and coverage matrices.
| name | yarstack-coderabbit-triage |
| description | Triage CodeRabbitAI review comments on current PR, fix legitimate issues, push, resolve threads |
| disable-model-invocation | true |
Process the current CodeRabbitAI review comments on the active branch/PR with real engineering judgment.
git branch --show-currentgh pr view --json number,url,headRefName,baseRefNameFetch review threads and keep only those where isResolved: false. Resolved threads are already handled — do not re-open them.
gh api graphql -f query='query($owner:String!,$repo:String!,$num:Int!){repository(owner:$owner,name:$repo){pullRequest(number:$num){reviewThreads(first:100){nodes{id isResolved comments(first:20){nodes{id author{login} body path line}}}}}}}' -f owner=<owner> -f repo=<repo> -F num=<num>
Then:
isResolved: truecoderabbitai / coderabbitai[bot]gh pr view <num> --comments (filter to CodeRabbitAI, skip anything already addressed in a later commit or reply)For every comment:
Real bug, broken edge case, unsafe logic, missing validation, bad error handling, real maintainability problem, incorrect assumption, misleading code, genuine test gap, or clear meaningful inconsistency.
Minor cleanup, style preference, low-value refactor, weak-payoff readability tweak, speculative improvement.
Implement only if: fix is tiny, clearly improves the code, and creates no noise. Otherwise skip.
Misunderstands code, ignores repo context, duplicates logic handled elsewhere, suggests a pattern that does not fit, adds unnecessary complexity, or is generic bot noise.
git log --oneline -10)For each CodeRabbitAI thread, reply concisely and resolve if fixed.
Reply to an inline thread:
gh api graphql -f query='mutation($id:ID!,$body:String!){addPullRequestReviewThreadReply(input:{pullRequestReviewThreadId:$id,body:$body}){comment{id}}}' -f id=<threadId> -f body='<reply>'
Mark thread resolved:
gh api graphql -f query='mutation($id:ID!){resolveReviewThread(input:{threadId:$id}){thread{isResolved}}}' -f id=<threadId>
Good:
Fixed — added nil handling in the error path.Good catch. Updated validation and added a test.Not changing this one — already enforced at the service layer; duplicating here would add noise.Skipping — suggested refactor adds complexity without real benefit.Bad:
Report: