# Fix what we found

Every issue comes with a fix, a person who usually makes it and a prompt your coding assistant can follow.

Start with the list under **What a stranger learns from your link** at the top of your report. Each issue says how to fix it and who usually does it, so you can make the change yourself or pass it on.

## Fix it with your coding assistant

Most fixes are a small change to a setting, a header or a file. If you build your site with a coding assistant, Lockpick writes the instructions for it.

1. Open the issue and choose **Copy fix prompt**. To hand over every issue at once, choose **Copy prompt to fix all**.
2. Paste the prompt into your assistant, for example Claude Code, Codex, Cursor, VS Code, OpenCode, Lovable, Bolt.new, Replit or v0.
3. Review the change it makes before you publish it.

The prompts tell the assistant to work on a new branch and not to deploy, push or change your DNS on its own, so you stay in control.

If your assistant runs in a terminal, open **More ways to copy the fix** and choose **Copy CLI command**. It copies one command that starts the assistant with the fix loaded. The command only works for a short time, so paste it straight away.

```bash title="Terminal"
# The shape of the command. Yours carries its own short-lived link.
p=$(curl -fsSL <your-fix-link>) && claude "$p"
```

## Fix it yourself

Some fixes happen outside your code, such as a DNS record or an email setting at your domain provider. The card names where the change is made, and **See it for yourself** links to the public record so you can watch it change.

> **Good to know**
>
> Share the Technical view with your developer. It has the evidence and the
> standard references they will look for.

## Then check again

When you have made a change, [check again](/docs/get-started/check-again) to confirm it worked.