Prompt·Correctness and reliability·R01
Safe to run twice?
Finds actions that do damage when they run twice: double sends, double charges, duplicate rows.
Prompt
Find operations that cannot safely be retried. Examine duplicate events, partial failures, idempotency, transaction boundaries, and recovery from interrupted execution.
- What it returns
- Each operation with its trigger, what a second run does, and whether a key or constraint prevents it.
- Skip it when
- Actions that only read data.
- Changes
- Changes nothing
- Sessions
- Look first, then fix in a new session
- Tools
- Repository and read-only access to the database layout.
- Also called
- Retry and idempotency failures
Skills it uses
Related prompts
- Updates that overwrite each otherPromptFinds updates that overwrite newer data because two things wrote at once.
- Half-finished failuresPromptFinds what is left behind when something fails halfway.
- Imports that fail quietlyPromptFinds rows that go missing or land on the wrong record during import, with no error.
- Can we rerun everything without damaging the data?PromptImports get retried, schedulers overlap, files are replayed, or runs fail halfway.
More in Correctness and reliability.