principle-make-operations-idempotent
About principle-make-operations-idempotent
A coding skill for designing state-changing operations to reach the same correct state after retries, restarts, or partial failures. It is aimed at developers building resilient commands, lifecycle operations, and processing loops.
Key features
- 01Make repeated runs converge
- 02Reconcile state at startup
- 03Clean up by content equivalence
- 04Detect stale locks by PID
- 05Regenerate work after failed cycles
Use cases
- 01Make commands safe to retry
- 02Recover operations after crashes
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/principle-make-operations-idempotentin Claude Code to confirm it loaded.
Details
From the project READMEMake Operations Idempotent
Design operations so they converge to the correct state regardless of how many times they run or where they start from. Every state-mutating operation should answer: "What happens if this runs twice? What happens if the previous run crashed halfway?"
Why: Commands, lifecycle operations, and processing loops run where crashes, restarts, and retries are normal. If partial state changes the next run's outcome, every restart becomes a debugging session.
The pattern:
- Convergent startup: scan for existing state, clean stale artifacts, adopt live sessions
- Content-based cleanup: compare by content equivalence, not creation order
- Self-healing locks: use PID-based stale lock detection
- Idempotent scheduling: failed work respawns cleanly, fresh input regenerated after each cycle
The test:
- What happens if this runs twice in a row?
- What happens if the previous run crashed at every possible point?
- Does re-execution converge to the same end state?
If any answer is "it depends on what state was left behind," the operation needs a reconciliation step.