agentleFS
mihaimurra001mihaimurra001/preConfigProject/.claude/skills/concurrency-and-race-conditions/SKILL.md

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.

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
  1. Distinctive:

    Never check permissions or file existence in one step and then act on it in a separate unsynchronized step.

    line 25
  2. Very specific:

    Use atomic filesystem primitives (open(..., O_CREAT | O_EXCL)) or database constraints (unique keys, row-level locks via SELECT ...

    line 26
  3. Distinctive:

    Always attach finite TTLs to distributed locks (Redis Redlock, Postgres advisory locks) to avoid permanent deadlocks if a worker crashes.

    line 29
  4. Distinctive:

    Verify lock ownership token before releasing to prevent releasing another worker's acquired lock after a TTL timeout.

    line 30

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 via SELECT ... 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.