Agent skill · qodo-ai
qodo-review-resolver
Read or resolve a pull request's Qodo review with the qodo CLI — fetch structured status, reviewed commit SHA, and findings for ANY PR as JSON, with optional extended details and citation evidence for audits, then optionally resolve open findings and record outcomes, once or until clean. Use this — never `gh`/`curl` scraping of review comments — for "is the review clean on PR #N", "get Qodo's findings for <pr> as JSON", "audit the review evidence", "show finding citations", "what did Qodo flag", "is this review up to date with head", "check before merging", "resolve my PR review", "fix the review findings", or "babysit this PR until it's clean".
What it needs
About 12k tokens when loaded.
What this skill does
Read & Resolve Findings Description Use the qodo CLI to read a pull request's review session — its status, the commit that was reviewed, and every finding with its resolution status — for any PR (yours or someone else's). Request extended results when auditing citations or investigating a finding's supporting evidence, location, dismissal, or review-run history. Reading alone is a valid use: stop after the read to report where a review stands or what it flagged (e.g. to gate a merge on it being clean at head). To go further, resolve the open findings in code, applying your own judgment (the review is a strong second opinion, not gospel) — by default you evaluate the findings and let the user pick which to apply (pass autofix to apply directly), run once (report + resolve what the user approves) or as a watch loop (resolve → let Qodo re-review the new commit → repeat until clean). Then record the outcome on the findings you settled — mark-implemented for ones you fixed, dismiss for ones the user agreed to close without a code change. That is what clears the merge-policy block those findings hold; skip it and the review stays red until a human clicks through the PR. You still never post to the forge yourself: the status tools write Qodo's review DB and Qodo reconciles the PR comments. (Plain git/forge metadata reads — git rev-parse HEAD, gh pr view --json headRefOid — are fine and in fact required for the freshness check below; the "don't scrape" rule is about qodo, not your shell.) Prerequisites The Qodo CLI is authenticated and exposes the structured PR-review session tools. The exact PR URL and its current head SHA can be resolved without scraping review comments. Any write to a finding has the user's explicit authority or the skill's explicit autofix scope. Instructions Follow the detailed workflow below: fetch structured state, require a completed exact-head review, present open findings, apply only approved fixes, and record only outcomes actually settled. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills qodo-ai/qodo-review-resolver--8e2e39