Skip to main content

​
Overview

The /qodo-pr-resolver skill fetches Qodo PR review issues and helps you fix them interactively or in batch. It streamlines the code review process by automatically addressing reviewer feedback.

​
Features

Fetch Issues

Pull PR review comments from Qodo

Interactive Mode

Review and fix issues one at a time

Batch Mode

Auto-fix all issues in one pass

Smart Fixes

Applies context-aware fixes following coding rules

​
Prerequisites

  • Qodo API key configured in .env
  • Active pull request with Qodo review
  • Git repository with pending review issues

​
How to Apply

​
Interactive Mode (Default)

/qodo-pr-resolver
Claude will:
  1. Fetch PR review issues from Qodo
  2. Show each issue with file/line context
  3. Ask how you want to fix it
  4. Apply the fix
  5. Move to the next issue

​
Batch Mode

/qodo-pr-resolver --batch
Claude will:
  1. Fetch all issues
  2. Attempt to fix all automatically
  3. Show summary of fixes applied
  4. List any issues requiring manual intervention

​
What It Does

1

Fetch PR review

Retrieves review comments and suggestions from Qodo API.
2

Categorize issues

Groups by:
  • Auto-fixable (style, formatting)
  • Code changes needed (logic, structure)
  • Manual review required (design decisions)
3

Apply fixes

For each issue:
  • Shows file and line number
  • Explains the problem
  • Proposes a fix
  • Applies if approved (interactive) or auto-applies (batch)
4

Verify

Runs tests and linters to ensure fixes don’t break anything.

​
Usage Examples

​
Interactive Fix

@Andy /qodo-pr-resolver
Claude: 
Found 5 issues in PR #123:

1. src/auth.ts:42 - Missing input validation
   Reviewer: "Add email validation before processing"
   
   Suggested fix:
   + if (!isValidEmail(email)) {
   +   throw new Error('Invalid email');
   + }
   
   Apply this fix? (yes/no/skip)

​
Batch Fix

@Andy /qodo-pr-resolver --batch
Claude: 
Processing 5 issues...

✓ Fixed: Missing input validation (src/auth.ts:42)
✓ Fixed: Unused import (src/utils.ts:5)
✓ Fixed: Inconsistent naming (src/user.ts:28)
⚠ Manual: Complex refactoring needed (src/api.ts:100)
✗ Skipped: Design decision required (src/index.ts:15)

Summary:
- 3 auto-fixed
- 2 require manual review

​
Configuration

​
Environment Variables

​
QODO_API_KEY
string
required
API key from Qodo platform
​
QODO_PR_RESOLVER_MODE
string
Default mode: interactive or batch (default: interactive)

​
Command Options

OptionDescription
--batchAuto-fix all issues without prompting
--pr <number>Specify PR number (auto-detected if omitted)
--category <type>Only fix specific category (style, logic, security)

​
Issue Categories

​
Auto-fixable

  • Code style and formatting
  • Import organization
  • Unused variables
  • Simple refactorings

​
Code Changes

  • Input validation
  • Error handling
  • Performance optimizations
  • Security improvements

​
Manual Review

  • Architecture changes
  • Design decisions
  • Complex refactorings
  • Breaking changes

​
Verification

After fixes are applied: 
# Run tests
npm test

# Run linter
npm run lint

# Check git diff
git diff

​
Troubleshooting

Verify:
  • PR has Qodo review completed
  • API key has access to the repository
  • Correct branch is checked out
Check:
  • File has been modified since review
  • Merge conflicts exist
  • Line numbers have shifted
Try interactive mode to handle edge cases.
Some fixes may need adjustment. Use:
git reset HEAD~1  # Undo last commit
Then re-run in interactive mode to review each fix.

​
Best Practices

Start Interactive

Use interactive mode first to understand review feedback

Test After Each Fix

Run tests after applying fixes to catch issues early

Review Changes

Always review git diff before committing fixes

Commit Separately

Commit review fixes separately from feature work

Get Qodo Rules

Load coding rules before tasks

Customization

Customize review workflow

Build docs developers (and LLMs) love

Get started for freeTalk to us