Skip to main content
Every Octopoda finding comes with a fix prompt: instructions written for an AI coding tool that name the file, explain the issue and describe the change. You paste it into Cursor or Claude Code, review what the tool changes, and scan again to confirm the issue is gone.

​
Get the fix prompt

Open the finding. At the top, in Fix it, choose Cursor or Claude Code to get the prompt written for that tool, then select Copy fix prompt.If the finding has a suggested code change, See the code change shows it as a diff.

​
Apply and confirm the fix

1

Paste the prompt

Open the project in Cursor or Claude Code and paste the prompt into a new chat.
2

Review the change

Read the diff before you accept it. The prompt says what to change, but your AI tool writes the code, and it can get things wrong. Run your tests.
3

Scan again

Push the fix and let the pull request check scan it, or run octopoda scan. A finding that the new scan can no longer reproduce does not appear in it.

​
When a finding is marked fixed

Octopoda marks a finding Fixed automatically when a later full code scan of the same code re-tests it and can no longer reproduce it. The finding page then links to the scan that confirmed the fix. That happens on:
  • a code scan of a repository’s default branch, started with New scan in the web app, for findings in that repository;
  • a code scan from the CLI or your AI tool, for findings from earlier scans of the same project folder. Octopoda recognizes the project by the folder’s name, so scan from the same folder.
Pull request scans, and scans of other branches, don’t mark findings fixed. Merge the fix, then scan the default branch.