How do I install the Coderabbit Resolver skill?

Run npx skillmds@latest add tomevault-io/coderabbit-resolver in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Coderabbit Resolver safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Coderabbit Resolver?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Coderabbit Resolver free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Coderabbit Resolver?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Coderabbit Resolver by tomevault-io

Name: Coderabbit Resolver
Author: tomevault-io

Coderabbit Resolver

Automates the full CodeRabbit PR review cycle — extracts review comments, fixes code, commits, pushes, monitors CI, resolves threads, and repeats until all checks pass and threads are resolved, then merges and cleans up branches. Supports --bulk to process all open PRs sequentially. Use when asked to fix CodeRabbit reviews, resolve PR comments, or handle the complete review-fix-merge workflow.

tomevault-io c8c195a 2 files · 5.0 KB Updated Sep 17, 2026

File contents

Automates the iterative CodeRabbit review loop on a GitHub PR until all review comments are resolved and CI is green, then merges and cleans up.

Principle 1: GraphQL-Only Thread Resolution

GitHub has NO REST API for resolving review threads. You MUST use the GraphQL resolveReviewThread mutation with PRRT_-prefixed thread IDs. The mutation is idempotent — safe to call on already-resolved threads.

Principle 2: Iterative Loop Until Clean

The workflow runs in a loop:

Extract unresolved CodeRabbit review comments
Fix code issues OR resolve already-fixed threads
Commit → Push → Wait for CI + CodeRabbit re-review
Repeat until: zero unresolved threads AND all CI checks pass

Principle 3: Validation Before Every Push

Run pnpm validate (or project-specific validation) before every commit. Never push broken code.

Principle 4: Safe Merge and Cleanup

Only merge when ALL conditions are met: CI green, no unresolved threads, CodeRabbit check complete. After merge, delete remote branch and prune local.

Principle 5: Rate Limit Handling

CodeRabbit may hit API rate limits and post a comment instead of reviewing. When detected, the workflow automatically waits for the rate limit to expire (+ 30s buffer), then posts @coderabbitai full review to trigger a complete re-review. Max 3 rate limit retries per PR to prevent infinite loops.

/coderabbit-resolver <PR_NUMBER>       # Process single PR
/coderabbit-resolver 17                # Process PR #17
/coderabbit-resolver --bulk            # Process ALL open PRs (oldest first)

If no PR number provided (and no --bulk), detect from current branch:

gh pr view --json number -q .number

After obtaining the PR number, read and follow workflows/review-loop.md. If --bulk is specified, read and follow workflows/bulk-loop.md.

After reading the workflow, follow it exactly.

All in references/:

File	Content
github-graphql-api.md	GraphQL queries/mutations for thread resolution, CI status checks
coderabbit-commands.md	CodeRabbit bot commands and behavior reference

All in workflows/:

Workflow	Purpose
review-loop.md	The main iterative review-fix-resolve-merge loop (single PR)
bulk-loop.md	Process all open PRs sequentially (oldest first), merging each

Scripts

Script	Purpose
resolve-threads.sh	Resolve all unresolved CodeRabbit threads on a PR
check-ci-status.sh	Check CI and CodeRabbit review status for a PR
wait-for-ratelimit.sh	Detect CodeRabbit rate limit, wait for expiry, trigger full review

A successful --bulk invocation:

All open PRs processed (oldest first)
Each PR either MERGED or SKIPPED (with reason)
Summary report generated with results table

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: coderabbit-resolverdescription: Automates the full CodeRabbit PR review cycle — extracts review comments, fixes code, commits, pushes, monitors CI, resolves threads, and repeats until all checks pass and threads are resolved, then merges and cleans up branches. Supports --bulk to process all open PRs sequentially. Use when asked to fix CodeRabbit reviews, resolve PR comments, or handle the complete review-fix-merge workflow.---<essential_principles>## How This Skill WorksAutomates the iterative CodeRabbit review loop on a GitHub PR until all review comments are resolved and CI is green, then merges and cleans up.### Principle 1: GraphQL-Only Thread ResolutionGitHub has NO REST API for resolving review threads. You MUST use the GraphQL `resolveReviewThread` mutation with `PRRT_`-prefixed thread IDs. The mutation is idempotent — safe to call on already-resolved threads.### Principle 2: Iterative Loop Until CleanThe workflow runs in a loop:1. Extract unresolved CodeRabbit review comments2. Fix code issues OR resolve already-fixed threads3. Commit → Push → Wait for CI + CodeRabbit re-review4. Repeat until: zero unresolved threads AND all CI checks pass### Principle 3: Validation Before Every PushRun `pnpm validate` (or project-specific validation) before every commit. Never push broken code.### Principle 4: Safe Merge and CleanupOnly merge when ALL conditions are met: CI green, no unresolved threads, CodeRabbit check complete. After merge, delete remote branch and prune local.### Principle 5: Rate Limit HandlingCodeRabbit may hit API rate limits and post a comment instead of reviewing. When detected, the workflow automatically waits for the rate limit to expire (+ 30s buffer), then posts `@coderabbitai full review` to trigger a complete re-review. Max 3 rate limit retries per PR to prevent infinite loops.</essential_principles><intake>This skill accepts a PR number or `--bulk` flag as argument. Usage:```/coderabbit-resolver <PR_NUMBER> # Process single PR/coderabbit-resolver 17 # Process PR #17/coderabbit-resolver --bulk # Process ALL open PRs (oldest first)```If no PR number provided (and no `--bulk`), detect from current branch:```bashgh pr view --json number -q .number```**After obtaining the PR number, read and follow `workflows/review-loop.md`.****If `--bulk` is specified, read and follow `workflows/bulk-loop.md`.**</intake><routing>| Input | Action ||-------|--------|| PR number provided | Read `workflows/review-loop.md` and execute with that PR || No PR number | Auto-detect from current branch, then read `workflows/review-loop.md` || `--bulk` flag | Read `workflows/bulk-loop.md` and process all open PRs |**After reading the workflow, follow it exactly.**</routing><reference_index>## ReferencesAll in `references/`:| File | Content ||------|---------|| github-graphql-api.md | GraphQL queries/mutations for thread resolution, CI status checks || coderabbit-commands.md | CodeRabbit bot commands and behavior reference |</reference_index><workflows_index>## WorkflowsAll in `workflows/`:| Workflow | Purpose ||----------|---------|| review-loop.md | The main iterative review-fix-resolve-merge loop (single PR) || bulk-loop.md | Process all open PRs sequentially (oldest first), merging each |</workflows_index><scripts_index>## Scripts| Script | Purpose ||--------|---------|| resolve-threads.sh | Resolve all unresolved CodeRabbit threads on a PR || check-ci-status.sh | Check CI and CodeRabbit review status for a PR || wait-for-ratelimit.sh | Detect CodeRabbit rate limit, wait for expiry, trigger full review |</scripts_index><success_criteria>A successful coderabbit-resolver invocation (single PR):- [ ] All CodeRabbit review threads resolved (zero unresolved)- [ ] All CI checks passing (green), including fixes for unrelated CI failures- [ ] CodeRabbit review status is complete- [ ] PR merged successfully- [ ] Remote branch deleted- [ ] Local branch cleaned up (switched to main, pruned)A successful `--bulk` invocation:- [ ] All open PRs processed (oldest first)- [ ] Each PR either MERGED or SKIPPED (with reason)- [ ] Summary report generated with results table</success_criteria>---> Converted and distributed by [TomeVault](https://tomevault.io/claim/laststance) — claim your Tome and manage your conversions.

Frequently asked questions