transaction-concurrency-guard
Skill1 starsChanged 9 months agoMITView on GitHub
Prevent race conditions and lost updates by enforcing transaction boundaries, idempotency, and lock strategy. Use for write-path correctness under concurrent load.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- chaos-fuzz-runnerSkill
- data-migration-safetySkill
- external-integration-reliabilitySkill
- failure-forensicsSkill
- harmonization-operatorSkill
- hud-control-opsSkill
- mcp-policy-opsSkill
- search-index-tuningSkill
- smoke-gate-runnerSkill
- sync-conflict-playbookSkill
- track-contract-authorSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when multiple writes can happen in parallel.
- Distinctive: line 18
Add deterministic concurrency probes for:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Transaction Concurrency Guard
Use this skill when multiple writes can happen in parallel.
Workflow
- Identify critical write paths and conflict keys.
- Choose consistency strategy per path:
- optimistic version checks
- pessimistic row/record locking
- idempotency keys for retries
- Define transaction boundaries around invariants, not around controllers.
- Add deterministic concurrency probes for:
- duplicate submission
- out-of-order retry
- concurrent update same record
Failure Modes To Handle
- Lost updates from read-modify-write races.
- Deadlocks from unstable lock ordering.
- Duplicate side effects on retry.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.