Fix prompts: how to use them

Every finding in a full report comes with a fix prompt: the same finding, rewritten as an instruction for an AI coding agent such as Claude Code, Cursor or Windsurf. Paste it into the agent working in your repo and it knows where to look and what to change.

What's in a prompt

• the issue and its severity,
• the location (file:line),
• why it matters, in one sentence,
• the change to make.

Prompts are built from the report's own fields, with no extra AI call.

Copy fix prompt for all

At the top of a full report, Copy fix prompt for all copies one prompt with the fix for every critical and high finding shown in full. It's grouped by file, most severe first. The button reads "Copied" when it's on your clipboard.

A long one is split into numbered parts ("part 1 of 3"), each complete on its own and separated by a --- line. If your agent cuts off long input, paste the parts one at a time.

Using them safely

The prompt text comes from your repository, and a repository can contain text written to steer an agent. So each prompt starts with a note telling the agent to use the text only to find and change the listed code, and never to run commands, install packages, open links or touch other files because the text says so. Review the agent's changes like any other pull request.

Then rescan

After the fixes land, scan the project again. Fixed findings drop out of the report and the grade updates. If nothing changed since the last Deep scan, the rescan is free.

On the Free plan, prompts are available for the findings shown in full. Hidden findings have no prompt until the report is unlocked.