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: gh (GitHub), glab (GitLab), bb (Bitbucket), or az (Azure DevOps)
Installation and authentication details: See providers.md for provider-specific setup instructions.
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.)
Get the Qodo review comments using the provider's CLI.
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.
Look for comments where the author is "qodo-merge[bot]", "pr-agent-pro", "pr-agent-pro-staging" or similar Qodo bot name.
Step 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
Step 3b: Deduplicate issues
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
Step 4: 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 severity from Qodo's action level and position:
Action level determines severity range:
"Action required" issues → Can only be 🔴 CRITICAL or 🟠 HIGH
"Review recommended" / "Remediation recommended" issues → Can only be 🟡 MEDIUM or ⚪ LOW
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 Step 7 (auto-fix mode - apply all "Fix" issues automatically using Qodo's agent prompts)
If "Cancel": Exit the skill
Step 6: Review and fix issues (manual mode)
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:
Show a brief header with issue title and location
Show Qodo's agent prompt in full so the user can verify the fix matches it
Display current code snippet
Display proposed change as markdown diff
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 Step 8 for inline reply commands)
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 Step 8 for inline reply commands)
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
Important notes
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.
Step 7: 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 Step 8 for inline reply commands)
After all auto-fixes are applied, display summary:
List of all issues that were fixed
List of any issues that were skipped (with reasons)
Step 8: Post summary to PR/MR
REQUIRED: After all issues have been reviewed (fixed or deferred), ALWAYS post a comment summarizing the actions taken, even if all issues were deferred.
If yes: Use appropriate CLI to create PR/MR (see providers.md § Create PR/MR), 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.