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
Arguments
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
See also
pome inspect— read the run before you ask for a fix.pome run—--no-fix-promptskips assembling one for the cloud run.