Skip to main content
Review Resolver is one of the skills in the Agentic Toolbox. It enables your coding agent to retrieve and resolve Qodo Review findings directly from the agent workflow. After Qodo reviews an open pull request and posts findings, your agent can retrieve those findings, understand their context, and resolve them without leaving the development flow. Review Resolver combines Qodo Review findings with repository context to help investigate issues, apply fixes, and track the resolution status of every finding. The agent follows your instruction as a scope filter over the findings. It resolves only the findings you request, whether based on severity, category, a specific finding, or report-only mode. Every finding has an explicit outcome:
  • Fixed with an applied change.
  • Skipped with a reason.
  • Reported without changes.
Review Resolver does not blindly apply fixes. It operates within the scope of your request and ensures that findings are never silently ignored.

​
Supported interfaces

​
What you can do

With Review Resolver, you can:
  • Retrieve Qodo Review findings from an open pull request.
  • Resolve findings directly from your coding agent workflow.
  • Scope which findings should be addressed.
  • Apply fixes based on the finding context.
  • Track which findings were fixed, skipped, or reported.
  • Avoid manually switching between review results and your code editor.
  • Keep control over which findings are modified.

​
Common use cases

​
Resolve review findings

Resolve issues identified by Qodo Review after a pull request is opened. Use it to:
  • Retrieve findings from the current pull request.
  • Understand the reported issue.
  • Apply the required code changes.
  • Verify the resolution.
Example questions
  • Resolve the security findings from my pull request.
  • Fix all high-severity findings.
  • Resolve this specific finding.
Example workflow

​
Control the scope of resolution

Specify exactly which findings the agent should address. Use it to:
  • Filter findings by category.
  • Select a specific finding.
  • Limit changes to a requested scope.
  • Run in report-only mode.
Example questions
  • Resolve only security findings.
  • Fix this finding only.
  • Review findings but do not apply changes.
  • Report findings without modifying code.

​
Understand skipped findings

See why findings were not changed. Use it to:
  • Understand skipped findings.
  • Confirm that no findings were silently ignored.
  • Review whether additional action is needed.
Example questions
  • Why was this finding skipped?
  • Show me unresolved findings.
  • Which findings are outside the requested scope?

​
Keep the pull request clean

Continue resolving findings until the pull request meets the required quality level. Use it to:
  • Address remaining review feedback.
  • Re-run resolution after changes.
  • Ensure findings are either resolved or explicitly handled.
Example questions
  • Resolve the remaining findings.
  • Check if my pull request is clean.
  • Fix all reported issues that are in scope.

​
Frequently asked questions

Review Resolver uses Qodo Review findings together with repository context to understand issues and apply appropriate fixes.
No. Review Resolver only acts on findings that match your instruction. It does not widen the scope of the request.
Every finding has an explicit outcome. A finding is either fixed, skipped with a reason, or reported without changes.
No. Review Resolver uses the finding context and your requested scope to determine which changes to make.
Yes. You can scope resolution by severity, category, individual finding, or report-only mode.

​
Additional resources