Skills
Enhancement Official

Qodo

Fetch Qodo code review issues, auto-fix them, and enforce org-wide coding rules during generation.

What it does

  • Fetch and fix Qodo PR review issues interactively or in batch
  • Reply to inline review comments with fix decisions
  • Load org and repo coding rules before code generation
  • Supports GitHub, GitLab, Bitbucket, and Azure DevOps
  • Rules enforced by severity: error, warning, recommendation

What you'll need

  • NanoClaw installed and running
  • Qodo account with API key
  • A git repository with an open PR or MR

Install

/qodo-pr-resolver

How it works

NanoClaw integrates with Qodo through two complementary skills: /qodo-pr-resolver for fixing code review issues, and /get-qodo-rules for loading coding standards before writing code.

PR Resolver

The /qodo-pr-resolver skill finds the open PR or MR for your current branch, fetches all Qodo review comments (both summary-level and inline), and presents them in a prioritized table. Each issue is tagged with a severity — 🔴 Critical, 🟠 High, 🟡 Medium, or ⚪ Low — based on Qodo’s action level and position in the file.

You get three options:

  • Review each issue — the skill walks through issues one by one, shows the proposed fix and Qodo’s agent prompt, and asks for your approval before applying.
  • Auto-fix all — applies all fixes automatically using the agent prompts from Qodo’s review.
  • Cancel — skip without changes.

After fixes are applied, the skill posts a summary comment on the PR, resolves the Qodo review, and optionally pushes the changes to the remote.

The skill auto-detects your git provider (GitHub, GitLab, Bitbucket, or Azure DevOps) from the remote URL, so there’s no provider-specific configuration.

Coding Rules

The /get-qodo-rules skill loads your organization’s coding rules from Qodo before code generation or modification tasks. Rules are fetched at multiple scope levels:

  • Universal — applies to all repositories
  • Org level — applies to your organization
  • Repo level — applies to the current repository
  • Path level — applies to specific file paths

Rules are grouped by severity (error, warning, recommendation) and applied during code generation. After the task completes, the agent reports which rules were followed and flags any that couldn’t be satisfied.

Tips

  • Run /get-qodo-rules at the start of a coding session to front-load your team’s standards. The rules are cached for the session, so you don’t need to fetch them repeatedly.
  • The PR resolver works best when Qodo has already reviewed the PR. If no review comments exist, the skill will tell you and exit cleanly.
  • In auto-fix mode, the agent uses Qodo’s suggested prompts verbatim. If you want more control over how fixes are applied, use the interactive review mode instead.
  • Both skills require a QODO_API_KEY. Set it in your .env file or migrate it to Agent Vault with /init-onecli.