concurrency-and-race-conditions
Skill1 starsChanged 2 months agoMITView on GitHub
Use when writing shared state mutations, async job queues, inventory decrementing, or balance transfers. Prevents race conditions and double-spends.
In this repository55 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- accessibility-and-inclusive-designSkill
- animateSkill
- api-contracts-and-backward-compatSkill
- appsec-code-reviewSkill
- architecture-decision-recordsSkill
- code-review-and-qualitySkill
- code-simplificationSkill
- concurrency-and-race-conditionsSkill
- database-and-migrations-architectSkill
- dependency-vulnerability-auditSkill
- design-taste-frontendSkill
- emil-design-engSkill
- graphifySkill
- headroomSkill
- impeccableSkill
- incremental-implementationSkill
- observability-and-structured-loggingSkill
- planning-and-task-breakdownSkill
- ponytail-auditSkill
- ponytail-reviewSkill
- refactoring-legacy-codeSkill
- root-cause-analysis-and-postmortemSkill
- secret-scanningSkill
- shipping-and-launchSkill
- spec-driven-developmentSkill
- test-driven-developmentSkill
- threat-modelingSkill
- accessibility-and-inclusive-designSkill
- animateSkill
- api-contracts-and-backward-compatSkill
- appsec-code-reviewSkill
- architecture-decision-recordsSkill
- code-review-and-qualitySkill
- code-simplificationSkill
- database-and-migrations-architectSkill
- dependency-vulnerability-auditSkill
- design-taste-frontendSkill
- emil-design-engSkill
- graphifySkill
- headroomSkill
- impeccableSkill
- incremental-implementationSkill
- observability-and-structured-loggingSkill
- planning-and-task-breakdownSkill
- ponytail-auditSkill
- ponytail-reviewSkill
- refactoring-legacy-codeSkill
- root-cause-analysis-and-postmortemSkill
- secret-scanningSkill
- shipping-and-launchSkill
- spec-driven-developmentSkill
- test-driven-developmentSkill
- threat-modelingSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Never check permissions or file existence in one step and then act on it in a separate unsynchronized step.
- Very specific: line 26
Use atomic filesystem primitives (open(..., O_CREAT | O_EXCL)) or database constraints (unique keys, row-level locks via SELECT ...
- Distinctive: line 29
Always attach finite TTLs to distributed locks (Redis Redlock, Postgres advisory locks) to avoid permanent deadlocks if a worker crashes.
- Distinctive: line 30
Verify lock ownership token before releasing to prevent releasing another worker's acquired lock after a TTL timeout.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Concurrency, Race Conditions & State Integrity
Concurrent execution turns rare edge cases into frequent production corruptions:
1. Eliminate Read-Modify-Write Hazards
- Dangerous:
const user = await db.getUser(id); user.balance -= amount; await db.saveUser(user); - Safe (Atomic SQL Statement):
UPDATE accounts SET balance = balance - :amount, updated_at = NOW() WHERE id = :id AND balance >= :amount;
2. Time-of-Check to Time-of-Use (TOCTOU)
- Never check permissions or file existence in one step and then act on it in a separate unsynchronized step.
- Use atomic filesystem primitives (
open(..., O_CREAT | O_EXCL)) or database constraints (unique keys, row-level locks viaSELECT ... FOR UPDATE).
3. Distributed Locking Guardrails
- Always attach finite TTLs to distributed locks (Redis Redlock, Postgres advisory locks) to avoid permanent deadlocks if a worker crashes.
- Verify lock ownership token before releasing to prevent releasing another worker's acquired lock after a TTL timeout.
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.

