Qodo PR Resolver

Fetch Qodo review issues for your current branch's PR/MR, fix them interactively or in batch, and reply to each inline comment with the decision. Supports GitHub, GitLab, Bitbucket, and Azure DevOps.

Prerequisites

Required Tools:

• •Git - For branch operations
• •Git Provider CLI (one of):
  • •GitHub: gh CLI
    • •Install: brew install gh or cli.github.com
    • •Authenticate: gh auth login
  • •GitLab: glab CLI
    • •Install: brew install glab or glab.readthedocs.io
    • •Authenticate: glab auth login
  • •Bitbucket: bb CLI or API access
    • •See bitbucket.org/product/cli
  • •Azure DevOps: az CLI with DevOps extension
    • •Install: brew install azure-cli or docs.microsoft.com/cli/azure
    • •Install extension: az extension add --name azure-devops
    • •Authenticate: az login then az devops configure --defaults organization=https://dev.azure.com/yourorg project=yourproject

Required Context:

• •Must be in a git repository
• •Repository must be hosted on a supported git provider (GitHub, GitLab, Bitbucket, or Azure DevOps)
• •Current branch must have an open PR/MR
• •PR/MR must have been reviewed by Qodo (pr-agent-pro bot, qodo-merge[bot], etc.)

Quick Check:

git --version                                    # Check git installed
git remote get-url origin                        # Identify git provider
# Then check appropriate CLI:
gh --version && gh auth status                   # For GitHub
glab --version && glab auth status               # For GitLab
bb --version                                     # For Bitbucket
az --version && az devops                        # For Azure DevOps

Understanding Qodo Reviews

Qodo (formerly Codium AI) is an AI-powered code review tool that analyzes PRs/MRs with compliance checks, bug detection, and code quality suggestions.

Bot Identifiers

Look for comments from: pr-agent-pro, pr-agent-pro-staging, qodo-merge[bot], qodo-ai[bot]

Review Comment Types

1. •PR Compliance Guide 🔍 - Security/ticket/custom compliance with 🟢/🟡/🔴/⚪ indicators
2. •PR Code Suggestions ✨ - Categorized improvements with importance ratings
3. •Code Review by Qodo - Structured issues with 🐞/📘/📎 sections and agent prompts (most detailed)

Instructions

When the user asks for a code review, to see Qodo issues, or fix Qodo comments:

Step 0: Check code push status

Check for uncommitted changes, unpushed commits, and get the current branch.

Scenario A: Uncommitted changes exist

• •Inform: "⚠️ You have uncommitted changes. These won't be included in the Qodo review."
• •Ask: "Would you like to commit and push them first?"
• •If yes: Wait for user action, then proceed to Step 1
• •If no: Warn "Proceeding with review of pushed code only" and continue to Step 1

Scenario B: Unpushed commits exist (no uncommitted changes)

• •Inform: "⚠️ You have N unpushed commits. Qodo hasn't reviewed them yet."
• •Ask: "Would you like to push them now?"
• •If yes: Execute git push, inform "Pushed! Qodo will review shortly. Please wait ~5 minutes then run this skill again."
• •Exit skill (don't proceed - Qodo needs time to review)
• •If no: Warn "Proceeding with existing PR review" and continue to Step 1

Scenario C: Everything pushed (both empty)

• •Proceed to Step 1

1. •

   Detect git provider from the remote URL (git remote get-url origin) — match against github.com, gitlab.com, bitbucket.org, or dev.azure.com.

2. •

   Find the open PR/MR for this branch:

   GitHub:

   bash

   gh pr list --head <branch-name> --state open --json number,title
   

   GitLab:

   bash

   glab mr list --source-branch <branch-name> --state opened
   

   Bitbucket:

   bash

   # Use API or bb CLI
   bb pr list --source-branch <branch-name> --state OPEN
   

   Azure DevOps:

   bash

   az repos pr list --source-branch <branch-name> --status active --output json
   

3. •

   Get the Qodo review comments:

   Qodo typically posts both a summary comment (PR-level, containing all issues) and inline review comments (one per issue, attached to specific lines of code). You must fetch both.

   GitHub:

   bash

   # PR-level comments (includes the summary comment with all issues)
   gh pr view <pr-number> --json comments
   
   # Inline review comments (per-line comments on specific code)
   gh api repos/{owner}/{repo}/pulls/<pr-number>/comments
   

   GitLab:

   bash

   # All MR notes including inline comments
   glab mr view <mr-iid> --comments
   

   Bitbucket:

   bash

   # All PR comments including inline comments
   bb pr view <pr-id> --comments
   

   Azure DevOps:

   bash

   # PR-level threads (includes summary comments)
   az repos pr show --id <pr-id> --output json
   
   # All PR threads including inline comments
   az repos pr policy list --id <pr-id> --output json
   az repos pr thread list --id <pr-id> --output json
   

   Look for comments where the author is "qodo-merge[bot]", "pr-agent-pro", "pr-agent-pro-staging" or similar Qodo bot name.

3a. Check if review is still in progress:

• •If any comment contains "Come back again in a few minutes" or "An AI review agent is analysing this pull request", the review is still running
• •In this case, inform the user: "⏳ Qodo review is still in progress. Please wait a few minutes and try again."
• •Exit early - don't try to parse incomplete reviews

3b. Deduplicate issues across summary and inline comments:

• •Qodo posts each issue in two places: once in the summary comment (PR-level) and once as an inline review comment (attached to the specific code line). These will share the same issue title.
• •Qodo may also post multiple summary comments (Compliance Guide, Code Suggestions, Code Review, etc.) where issues can overlap with slightly different wording.
• •Deduplicate by matching on issue title (primary key - the same title means the same issue):
  • •If an issue appears in both the summary comment and as an inline comment, merge them into a single issue
  • •Prefer the inline comment for file location (it has the exact line context)
  • •Prefer the summary comment for severity, type, and agent prompt (it is more detailed)
  • •IMPORTANT: Preserve each issue's inline review comment ID — you will need it later (step 8) to reply directly to that comment with the decision
• •Also deduplicate across multiple summary comments by location (file path + line numbers) as a secondary key
• •If the same issue appears in multiple places, combine the agent prompts

1. •

   Parse and display the issues:

   • •Extract the review body/comments from Qodo's review
   • •Parse out individual issues/suggestions
   • •IMPORTANT: Preserve Qodo's exact issue titles verbatim — do not rename, paraphrase, or summarize them. Use the title exactly as Qodo wrote it.
   • •IMPORTANT: Preserve Qodo's original ordering — display issues in the same order Qodo listed them. Qodo already orders by severity.
   • •Extract location, issue description, and suggested fix
   • •Extract the agent prompt from Qodo's suggestion (the description of what needs to be fixed)

   Severity mapping — derive from Qodo's action level and position:

   1. •

      Action level determines severity range:

      • •"Action required" issues → Can only be 🔴 CRITICAL or 🟠 HIGH
      • •"Review recommended" issues → Can only be 🟡 MEDIUM or ⚪ LOW
   2. •

      Qodo's position within each action level determines the specific severity:

      • •Group issues by action level ("Action required" vs "Review recommended")
      • •Within each group, earlier positions → higher severity, later positions → lower severity
      • •Split point: roughly first half of each group gets the higher severity, second half gets the lower

   Example: 7 "Action required" issues would be split as:

   • •Issues 1-3: 🔴 CRITICAL
   • •Issues 4-7: 🟠 HIGH
   • •Result: No MEDIUM or LOW issues (because there are no "Review recommended" issues)

   Example: 5 "Action required" + 3 "Review recommended" issues would be split as:

   • •Issues 1-2 or 1-3: 🔴 CRITICAL (first ~half of "Action required")
   • •Issues 3-5 or 4-5: 🟠 HIGH (second ~half of "Action required")
   • •Issues 6-7: 🟡 MEDIUM (first ~half of "Review recommended")
   • •Issue 8: ⚪ LOW (second ~half of "Review recommended")

   Action guidelines:

   • •🔴 CRITICAL / 🟠 HIGH: Always "Fix"
   • •🟡 MEDIUM: Usually "Fix", can "Defer" if low impact
   • •⚪ LOW: Can be "Defer" unless quick to fix

Output format - Display as a markdown table in Qodo's exact original ordering (do NOT reorder by severity - Qodo's order IS the severity ranking):

Qodo Issues for PR #123: [PR Title]

1. •

   Ask user for fix preference: After displaying the table, ask the user how they want to proceed using AskUserQuestion:

   Options:

   • •🔍 "Review each issue" - Review and approve/defer each issue individually (recommended for careful review)
   • •⚡ "Auto-fix all" - Automatically apply all fixes marked as "Fix" without individual approval (faster, but less control)
   • •❌ "Cancel" - Exit without making changes

   Based on the user's choice:

   • •If "Review each issue": Proceed to step 6 (manual review)
   • •If "Auto-fix all": Skip to auto-fix mode (apply all "Fix" issues automatically using Qodo's agent prompts)
   • •If "Cancel": Exit the skill
2. •

   Review and fix issues (if "Review each issue" was selected):

   • •For each issue marked as "Fix" (starting with CRITICAL):
     • •Read the relevant file(s) to understand the current code
     • •Implement the fix by executing the Qodo agent prompt as a direct instruction. The agent prompt is the fix specification — follow it literally, do not reinterpret or improvise a different solution. Only deviate if the prompt is clearly outdated relative to the current code (e.g. references lines that no longer exist).
     • •Calculate the proposed fix in memory (DO NOT use Edit or Write tool yet)
     • •Present the fix and ask for approval in a SINGLE step:
       1. •Show a brief header with issue title and location
       2. •Show Qodo's agent prompt in full so the user can verify the fix matches it
       3. •Display current code snippet
       4. •Display proposed change as markdown diff
       5. •Immediately use AskUserQuestion with these options:
          • •✅ "Apply fix" - Apply the proposed change
          • •⏭️ "Defer" - Skip this issue (will prompt for reason)
          • •🔧 "Modify" - User wants to adjust the fix first
     • •WAIT for user's choice via AskUserQuestion
     • •If "Apply fix" selected:
       • •Apply change using Edit tool (or Write if creating new file)
       • •Reply to the Qodo inline comment with the decision (see inline reply commands below)
       • •Git commit the fix: git add <modified-files> && git commit -m "fix: <issue title>"
       • •Confirm: "✅ Fix applied, commented, and committed!"
       • •Mark issue as completed
     • •If "Defer" selected:
       • •Ask for deferral reason using AskUserQuestion
       • •Reply to the Qodo inline comment with the deferral (see inline reply commands below)
       • •Record reason and move to next issue
     • •If "Modify" selected:
       • •Inform user they can make changes manually
       • •Move to next issue
   • •Continue until all "Fix" issues are addressed or the user decides to stop
3. •

   Auto-fix mode (if "Auto-fix all" was selected):

   • •For each issue marked as "Fix" (starting with CRITICAL):
     • •Read the relevant file(s) to understand the current code
     • •Implement the fix by executing the Qodo agent prompt as a direct instruction. The agent prompt is the fix specification — follow it literally, do not reinterpret or improvise a different solution. Only deviate if the prompt is clearly outdated relative to the current code (e.g. references lines that no longer exist).
     • •Apply the fix using Edit tool
     • •Reply to the Qodo inline comment with the decision (see inline reply commands below)
     • •Git commit the fix: git add <modified-files> && git commit -m "fix: <issue title>"
     • •Report each fix with the agent prompt that was followed:

       ✅ Fixed: [Issue Title] at [Location] Agent prompt: [the Qodo agent prompt used]

     • •Mark issue as completed
   • •After all auto-fixes are applied, display summary:
     • •List of all issues that were fixed
     • •List of any issues that were skipped (with reasons)

IMPORTANT: Single-step approval with AskUserQuestion:

• •NO native Edit UI (no persistent permissions possible)
• •Each fix requires explicit approval via custom question
• •Clearer options, no risk of accidental auto-approval

CRITICAL: Single validation only - do NOT show the diff separately and then ask. Combine the diff display and the question into ONE message. The user should see: brief context → current code → proposed diff → AskUserQuestion, all at once.

Example: Show location, Qodo's guidance, current code, proposed diff, then AskUserQuestion with options (✅ Apply fix / ⏭️ Defer / 🔧 Modify). Wait for user choice, apply via Edit tool if approved.

Special cases:

• •

  Unsupported git provider: If the remote URL doesn't match GitHub, GitLab, Bitbucket, or Azure DevOps, inform the user and exit

• •

  No PR/MR exists:

  • •Inform: "No PR/MR found for branch <branch-name>"
  • •Ask: "Would you like me to create a PR/MR?"
  • •If yes: Use appropriate CLI to create PR/MR (gh pr create / glab mr create / bb pr create / az repos pr create), then inform "PR created! Qodo will review it shortly. Run this skill again in ~5 minutes."
  • •If no: Exit skill
  • •IMPORTANT: Do NOT proceed without a PR/MR
• •

  No Qodo review yet:

  • •Check if PR/MR has comments from Qodo bots (pr-agent-pro, qodo-merge[bot], etc.)
  • •If no Qodo comments found: Inform "Qodo hasn't reviewed this PR/MR yet. Please wait a few minutes for Qodo to analyze it."
  • •Exit skill (do NOT attempt manual review)
  • •IMPORTANT: This skill only works with Qodo reviews, not manual reviews
• •

  Review in progress: If "Come back again in a few minutes" message is found, inform user to wait and try again, then exit

• •

  Missing CLI tool: If the detected provider's CLI is not installed, provide installation instructions and exit

  Inline reply commands (used per-issue in steps 6 and 7):

  Use the inline comment ID preserved during deduplication (step 3b).

  GitHub:

  bash

  gh api repos/{owner}/{repo}/pulls/<pr-number>/comments/<inline-comment-id>/replies -X POST -f body='<reply-body>'
  

  GitLab:

  bash

  glab api "/projects/:id/merge_requests/<mr-iid>/discussions/<discussion-id>/notes" -X POST -f body='<reply-body>'
  

  Bitbucket:

  bash

  bb api "/2.0/repositories/{workspace}/{repo}/pullrequests/<pr-id>/comments" -X POST -f 'content.raw=<reply-body>' -f 'parent.id=<inline-comment-id>'
  

  Azure DevOps:

  bash

  az repos pr thread comment add --id <pr-id> --thread-id <thread-id> --content '<reply-body>'
  

  Reply format:

  • •Fixed: ✅ **Fixed** — <brief description of what was changed>
  • •Deferred: ⏭️ **Deferred** — <reason for deferring>

  Keep replies short (one line). If a reply fails, log it and continue.

1. •

   Post summary to PR/MR (ALWAYS): REQUIRED: After all issues have been reviewed (fixed or deferred), ALWAYS post a comment summarizing the actions taken, even if all issues were deferred:

   Post a comment using the provider's CLI (gh pr comment / glab mr comment / bb pr comment / az repos pr thread create) with this format:

   markdown

   ## Qodo Fix Summary
   
   Reviewed and addressed Qodo review issues:
   
   ### ✅ Fixed Issues
   - **Issue Title** (Severity) - Brief description of what was fixed
   
   ### ⏭️ Deferred Issues
   - **Issue Title** (Severity) - Reason for deferring
   
   ---
   *Generated by Qodo PR Resolver skill*
   

   After posting the summary, resolve the Qodo review comment:

   Find the Qodo "Code Review by Qodo" comment by fetching all PR/MR comments, matching a Qodo bot author whose body contains "Code Review by Qodo".

   • •GitHub: Fetch comments via gh pr view <pr-number> --json comments, find the comment ID, then react with: gh api "repos/{owner}/{repo}/issues/comments/<comment-id>/reactions" -X POST -f content='+1'
   • •GitLab: Fetch discussions via glab api "/projects/:id/merge_requests/<mr-iid>/discussions", find the discussion ID, then resolve: glab api "/projects/:id/merge_requests/<mr-iid>/discussions/<discussion-id>" -X PUT -f resolved=true
   • •Bitbucket: Fetch comments via bb api, find the comment ID, then update to resolved status.

   If resolve fails (comment not found, API error), continue — the summary comment is the important part.

2. •

   Push to remote: If any fixes were applied (commits were created in steps 6/7), ask the user if they want to push:

   • •If yes: git push
   • •If no: Inform them they can push later with git push

   Important: If all issues were deferred, there are no commits to push — skip this step.