CodeRabbit Feedback Resolver

Process and resolve CodeRabbit's automated PR review comments systematically.

PR Comments Prohibition (CRITICAL)

NEVER leave new comments directly on GitHub PRs. This is strictly forbidden:

gh pr review --comment - FORBIDDEN
gh pr comment - FORBIDDEN
Any GraphQL mutation that creates new reviews or PR-level comments - FORBIDDEN

Permitted operations:

Reply to EXISTING CodeRabbit threads using addPullRequestReviewThreadReply
Resolve CodeRabbit threads using resolveReviewThread

WHEN TO USE THIS SKILL

USE THIS SKILL PROACTIVELY when ANY of the following occur:

User says "check rabbit review" / "handle coderabbit comments" / "resolve rabbit feedback"
User mentions "coderabbit" or "rabbit" and "PR" or "comments" in the same context
After PR creation when CodeRabbit has reviewed the PR
As part of the PR workflow after pr-reviewer skill completes
When PR checks show CodeRabbit has left review comments

CodeRabbit Comment Structure

CodeRabbit comments follow a structured markdown format:

_🧹 Nitpick_ | _🔵 Trivial_    <- Severity indicator (optional)

[Main feedback text]

<details>
<summary>💡 Optional suggestion</summary>
[Expanded suggestion content]
</details>

<details>
<summary>📝 Committable suggestion</summary>
[Code block with suggested changes]
</details>

<details>
<summary>🤖 Prompt for AI Agents</summary>
[Explicit instructions for AI to follow]
</details>

Key elements to extract:

Severity: _🧹 Nitpick_ or _🔵 Trivial_ = auto-resolvable
Prompt for AI Agents: Explicit instructions - USE THESE DIRECTLY
Committable suggestion: Ready-to-apply code changes

Prerequisites

CRITICAL: Load the fx-dev:github skill FIRST before running any GitHub API operations. This skill provides essential patterns and error handling for gh CLI commands.

Core Workflow

0. Verify CodeRabbit Configuration (First Run Only)

Before processing feedback, ensure CodeRabbit is configured to read REVIEW.md and AGENTS.md.

REVIEW.md (repo root) is the canonical review-conventions file for every automated reviewer; AGENTS.md holds project conventions. CodeRabbit's knowledge_base.code_guidelines feature reads instruction files to understand both. Its defaults cover **/AGENTS.md and **/CLAUDE.md — but not **/REVIEW.md, so the config below is what gets the review conventions to CodeRabbit. See fx-dev:setup → references/instruction-files.md for the full standard.

Check Configuration

# Canonical files present?
test -f REVIEW.md && echo "REVIEW.md exists" || echo "REVIEW.md MISSING - run fx-dev:setup"

# Check if .coderabbit.yaml exists
if [ -f ".coderabbit.yaml" ]; then
  cat .coderabbit.yaml
else
  echo "No .coderabbit.yaml found - using defaults"
fi

If REVIEW.md is missing, create it directly — just the file, with a # PR Review heading. Do NOT run fx-dev:setup or fx-dev:upgrade from here: setup also scaffolds docs/, AGENTS.md, CLAUDE.md, and .coderabbit.yaml, and this skill pushes to an open PR, so that would bury one review rule in a large unrelated diff. Mention that /fx-dev:setup will complete the layout later.

Configuration States

State	Action
No `.coderabbit.yaml` exists	Create it with the config below
Exists, `knowledge_base.code_guidelines.enabled: false`	Do not flip it. Someone disabled code guidelines deliberately, and this skill is mid-PR — silently re-enabling it commits an unrelated behavioural change. Report it, note that CodeRabbit will keep reviewing without the project's conventions, and let the user decide (`/fx-dev:upgrade` handles it with confirmation)
Exists, `enabled: true`, no `**/REVIEW.md` in `filePatterns`	Add `"**/REVIEW.md"` — including when `filePatterns` is absent entirely, since the defaults do not cover it
Exists, `enabled: true`, `**/REVIEW.md` already present	No action needed

The only state needing no action is the last one. enabled: true by itself is not sufficient: CodeRabbit's defaults cover **/AGENTS.md and **/CLAUDE.md but never root REVIEW.md, so without the explicit pattern it reviews with no knowledge of the review conventions.

Create/Update Configuration

Create or modify .coderabbit.yaml:

# .coderabbit.yaml
# Ensures CodeRabbit reads review conventions from REVIEW.md.
# AGENTS.md is already covered by CodeRabbit's default patterns.

knowledge_base:
  code_guidelines:
    enabled: true
    # Custom patterns APPEND to the defaults, they do not replace them.
    # REVIEW.md is not in CodeRabbit's defaults, so list it explicitly.
    filePatterns:
      - "**/REVIEW.md"

Patterns are case-sensitive: review.md does not match **/REVIEW.md.

When to Update REVIEW.md

If CodeRabbit feedback conflicts with project conventions (INCORRECT category), document the correct pattern in REVIEW.md. Since every reviewer reads it, one entry stops Copilot, CodeRabbit, Codex, and Claude Code Review from flagging it again.

Never create or edit .github/copilot-instructions.md — it is obsolete; Copilot reads REVIEW.md directly.

1. Fetch Unresolved CodeRabbit Threads

Query review threads using GraphQL.

IMPORTANT: Use inline values, NOT $variable syntax. The $ character causes shell escaping issues (Expected VAR_SIGN, actual: UNKNOWN_CHAR).

# Replace OWNER, REPO, PR_NUMBER with actual values
gh api graphql -f query='
query {
  repository(owner: "OWNER", name: "REPO") {
    pullRequest(number: PR_NUMBER) {
      reviewThreads(first: 100) {
        nodes {
          id
          isResolved
          path
          line
          comments(first: 10) {
            nodes {
              author { login }
              body
            }
          }
        }
      }
    }
  }
}'

Filter for: isResolved: false AND author login contains coderabbitai

2. Categorize Each Comment

For each unresolved CodeRabbit comment:

Category	Indicator	Action
Nitpick/Trivial	Contains `_🧹 Nitpick_` or `_🔵 Trivial_`	Auto-resolve immediately
Actionable with AI Prompt	Has `🤖 Prompt for AI Agents` section	Extract prompt, delegate to coder
Actionable with Committable	Has `📝 Committable suggestion`	Apply suggestion directly
General Feedback	No special sections	Analyze and delegate to coder
Deferred	Valid but out of scope for this PR	Track in PROJECT.md, reply, resolve

3. Process Each Category

Nitpicks/Trivial

Resolve immediately without changes
These are suggestions, not requirements

Actionable with AI Prompt (PREFERRED)

When a comment contains 🤖 Prompt for AI Agents, extract and use it directly:

Parse the comment body to extract content between <summary>🤖 Prompt for AI Agents</summary> and the closing </details>
The extracted text contains explicit instructions - pass these to the coder sub-agent verbatim
After fix is implemented, resolve the thread

Example extraction:

In src/lib/view-config.ts around lines 115 to 118, expand the JSDoc above
NUMERIC_OPERATORS to explicitly state that operators in this set expect numeric
values...

Actionable with Committable Suggestion

Extract the code block from 📝 Committable suggestion section
Apply the suggested changes directly using Edit tool
Commit with message referencing the CodeRabbit suggestion
Resolve the thread

General Feedback

Read the feedback carefully
Determine if it's valid or conflicts with project conventions
If valid: Delegate to coder sub-agent with context
If conflicts with project conventions (INCORRECT):
- Reply with explanation and resolve
- Update REVIEW.md to document the correct pattern
- This prevents Copilot, CodeRabbit, Codex, AND Claude Code Review from flagging it again — they all resolve to the same file

Deferred (Out of Scope)

When feedback is valid but out of scope for the current PR:

Load the fx-dev:project-management skill to track the follow-up work
Add task to PROJECT.md under the appropriate feature/section:
- Read current PROJECT.md structure
- Add a concise task describing the improvement
- Commit the PROJECT.md update
Reply to the thread explaining the deferral:
- "Valid suggestion. Tracked as follow-up task in PROJECT.md for a future PR."
Resolve the thread

CRITICAL: Never defer feedback without tracking it. "Acknowledged for follow-up" without a PROJECT.md entry is INCOMPLETE WORK.

4. Resolve Threads

Use GraphQL mutation to resolve each processed thread.

IMPORTANT: Use inline values, NOT $variable syntax.

# Replace THREAD_ID with actual thread ID (e.g., PRRT_kwDONZ...)
gh api graphql -f query='
mutation {
  resolveReviewThread(input: {threadId: "THREAD_ID"}) {
    thread { isResolved }
  }
}'

5. Reply to Threads (When Needed)

For feedback that conflicts with conventions or is being declined.