atomic-state-mutation SKILL.md skillA
atomic-state-mutation from annatchijova/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add annatchijova/skills/atomic-state-mutation@git:20260708.f31c428Pins git:20260708.f31c428 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- annatchijova/skills
- Path
atomic-state-mutation/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260708.f31c428, committed Jul 8, 2026
- Size
- 5,033 bytes
- Repository stars
- 9
- License
- a license file GitHub does not identify
Make a logical operation that spans several writes to persistent state land all-or-nothing, isolated from concurrent writers, with dependents cleaned up in the same transaction. Use this whenever one conceptual operation involves multiple writes — insert-then-delete, merge, consolidate, migrate, move-across-tables, write-plus-cascade — and a crash or a concurrent writer between steps would leave the store inconsistent; and whenever you hit "database is locked", duplicated rows after a merge…
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
# Atomic State Mutation A single logical operation that touches persistent state in several steps — insert the merged record, delete its sources, clean up their links — is only correct if it is *indivisible*. The moment those steps commit separately, two things can break it: a crash between commits (leaving the store half-mutated) and a concurrent writer slipping in between your read and your write (acting on state you were about to change). Both produce the same class of bug: duplicated data, double-counted aggregates, derived indexes built over a corrupted set — and all of it looks fine until something reads it. ## The six rules **1. All-or-nothing in one transaction.** If "insert merged node" and "delete sources" are separate commits, a crash between them leaves *both* alive: the merged record and the originals it was supposed to replace. Now you have duplicated content, recall counts tallied twice, and any field rebuilt over the active set (an index, a PCA, an aggregate) computed over a space that contains both copies. Wrap the entire logical operation in one transaction, commit once at the end, and roll back on any exception. The unit of atomicity is the *logical*… …
Read the whole file at its exact version.
How to install
mdr add annatchijova/skills/atomic-state-mutation@sha256:6f50be718a587f80The line at the top of this page pins the label git:20260708.f31c428, 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.
[](https://markdownregistry.com/a/art_bvhgqpbqnh2ywcxn)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 8, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5033 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
annatchijova/skills · 9 stars · license a license file GitHub does not identify · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bvhgqpbqnh2ywcxn GET https://markdownregistry.com/api/v1/resolve?ref=annatchijova/skills/atomic-state-mutation GET https://markdownregistry.com/api/v1/blob/6f50be718a587f801d9c7794a6cd431b8ad1342583facda4c9c7333d48ff35cf
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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.