Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of partial prior runs.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Make 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:**
1. What happens if this runs twice in a row?
2. What happens if the previous run crashed at every possible point?
3. 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.
The line at the top of this page pins the label git:20260827.04830a9, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_luj2w65iviyd4jbw
GET https://markdownregistry.com/api/v1/resolve?ref=painhardcore/pstack/principle-make-operations-idempotent
GET https://markdownregistry.com/api/v1/blob/6ff9aed07af7c3e57c4ef247f1a236b6ffdd1b294732cfedb9845413395d659c
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
painhardcore/pstack · .opencode/skills/architect/SKILL.md · Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use…
painhardcore/pstack · .opencode/skills/arena/SKILL.md · Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for…
painhardcore/pstack · .opencode/skills/blast-radius/SKILL.md · Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe…
painhardcore/pstack · .opencode/skills/create-verification-skill/SKILL.md · Generate a project-local verification skill that drives your app the way a user does — any language, framework, or…
painhardcore/pstack · .opencode/skills/figure-it-out/SKILL.md · Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a…
painhardcore/pstack · .opencode/skills/how/SKILL.md · Explain how a subsystem works, trace a runtime flow, or determine where code and ownership belong before making a…
painhardcore/pstack · .opencode/skills/interrogate/SKILL.md · Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find…
painhardcore/pstack · .opencode/skills/principle-boundary-discipline/SKILL.md · Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI…
cursor/plugins · harness/pstack/claude-code/skills/principle-make-operations-idempotent/SKILL.md · Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries…
cursor/plugins · pstack/skills/principle-make-operations-idempotent/SKILL.md · Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries…
michael-denyer/pstack-claude · plugins/pstack/skills/principle-make-operations-idempotent/SKILL.md · Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries…
backnotprop/pstack · skills/principle-make-operations-idempotent/SKILL.md · Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries…
j-star-films-studios/vibecode-protocol-suite · assets/.agent/skills/engineering-principles/make-operations-idempotent/SKILL.md · Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries…
creedants/pstack-t3 · skills/principle-make-operations-idempotent/SKILL.md · Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries…
arjitj2/open-pstack · plugins/pstack/skills/principle-make-operations-idempotent/SKILL.md · Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries…
shiwenbin1617/pstack · skills/principle-make-operations-idempotent/SKILL.md · Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries…