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

# pome fix-prompt

> Assemble a paste-into-IDE prompt from a failed run set.

`pome fix-prompt` turns a failed run into a prompt you can paste into your IDE.

It makes no model call and no network call. Everything it emits comes from
artifacts already on disk: the cloud verdicts persisted as `verdict.json` become
grouped failure signatures over the raw traces, in one prompt.

## Usage

```bash theme={"dark"}
pome fix-prompt [target] [task]
```

## Arguments

| Argument   | Required | Description                                                                                                    |
| ---------- | -------- | -------------------------------------------------------------------------------------------------------------- |
| `[target]` | No       | Artifacts root, or one trial run directory. Defaults to `runs`, where it reads the most recent failed run set. |
| `[task]`   | No       | Path to the task `.md` file. Required only with the legacy `events.jsonl` form below.                          |

## What it reads

With no arguments, `pome fix-prompt` finds the latest **failed** run set under
`./runs` and groups its failures by signature, so repeated instances of one defect
appear once rather than N times.

Point it at a single trial run directory to target that set instead.

The two-argument form, `pome fix-prompt <events.jsonl> <task.md>`, still works and
covers one trace at a time. It is the legacy shape; prefer the run-set form, which
sees the failure pattern across trials.

## Examples

```bash theme={"dark"}
# The latest failed run set
pome fix-prompt

# One trial group
pome fix-prompt runs/01-bug-happy-path/ses_abc123

# Legacy single-trace form
pome fix-prompt runs/01-bug-happy-path/ses_abc123/events.jsonl \
  tasks/01-bug-happy-path.md
```

## See also

* [`pome inspect`](./inspect) — read the run before you ask for a fix.
* [`pome run`](./run) — `--no-fix-prompt` skips assembling one for the cloud run.
