> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usebench.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Review and apply fixes

> Use evaluation evidence to improve prompts, models, tools and workflows.

## Copy this into your coding agent

Paste into Cursor, Codex, Claude Code, or another coding agent in your project.

```text theme={null}
Investigate a Bench finding using https://docs.usebench.ai/guides/automatic-fixes.
Use my saved fix brief or Bench MCP to read the failed case and evaluated revision.
Reproduce the failure, then inspect the prompt, tool code and workflow to find its cause.
Propose a focused fix and test it against the same criteria and previously passing cases.
Show the diff and results. Do not open a PR or deploy without my instruction.
```

## Start with a failed case

Open **History**, choose a bench and select **View details → Fixes**. Compare the
original prompt with the proposed prompt or model, and read why Bench recommends
the change. Review quality and cost together.

## Share the evidence with your coding agent

Choose **Prepare fix prompt**, then **Copy prompt**. The prompt includes the failed
case, the expected behavior and the evaluated code revision. You can also download
**Fix brief**, or ask your connected coding agent to use `bench_get_fix_brief`.
Reading a fix brief does not use an evaluation.

A coding agent can investigate prompt instructions, model configuration, tool code
or workflow logic. A failed test identifies behavior to investigate; it does not
by itself prove which part caused the failure.

Share briefs only with tools you approve: they can contain your source code and
evaluation data. Review the proposed changes before running or applying them.

## Test the change

1. Reproduce the original failure.
2. Apply the proposed change to a test branch.
3. Run the same case again, keeping its expected result and criteria unchanged.
4. Run previously passing cases to check for regressions.
5. Use independent cases that were not used to create the fix.

[Real app testing](/sdk/system-evaluation) check the actual tool calls and final
outcome. A higher prompt score alone does not prove that a tool or workflow works.

## Review before rollout

If you create a pull request through Bench or MCP, review its repository, branch,
files and test evidence. Creating a pull request does not merge or deploy it.
After deployment, use production evidence to check that the original problem is
resolved for real users.

Continue with [validation](/guides/validation) and [production checks](/sdk/production-checks).