Compare Prompt Versions

Track a prompt across revisions and see what each edit changed, which is the only way to attribute an output shift to the edit that caused it.

How to use
  1. Paste each version of the prompt in order.
  2. Compare consecutive revisions.
  3. Read what each edit changed.
Frequently asked questions
How is this different from a plain diff?
It is built around a chain of revisions rather than two texts, so you can walk a prompt through its history and see which step introduced a change.
Why track prompt versions?
Because prompt edits behave like code changes without the safety net. Without a history, a regression cannot be attributed to the edit that caused it.
What should I record alongside each version?
The date, what you were trying to fix, and how the outputs changed. The diff shows what moved; only your note explains why you moved it.
Should prompts live in version control?
Ideally yes, in the repo next to the code that sends them. This tool is for the exploratory phase before a prompt settles down enough to commit.
 Last updated 
Powered by maratool