Skip to content
Back to skills

Concurrency Control

ASecurity

`analysis-agent`/`task-agent`/`review-agent`: primary-Skill-selected for races, locks, optimistic conflicts, or worker overlap; never task owner; skip without concurrency impact.

  • 7 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 8, 2026
testing

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned September 22, 2026

npx -y skills add machenjie/rd-skills --skill concurrency-control --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Concurrency Control?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Concurrency Control
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/machenjie-concurrency-control/badge)](https://www.skillsdirectory.com/skills/machenjie-concurrency-control)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: concurrency-control
description: "`analysis-agent`/`task-agent`/`review-agent`: primary-Skill-selected for races, locks, optimistic conflicts, or worker overlap; never task owner; skip without concurrency impact."
---

# concurrency-control

## Registry Trigger

**Use when**

- control concurrent writes races locks leases optimistic conflicts and queues

**Do not use when**

- no task-local concurrency control decision is required

## Skill Role

Preserve named invariants under overlapping writes, retries, leases, redelivery, and stale ownership.

## High-Value Rules

- Select the narrowest current-store control that preserves the named invariant under reachable overlap.
- Define conflict outcomes, retry and idempotence, lock or lease lifecycle, order, and fencing for affected actors.
- Prove allowed and forbidden concurrent outcomes.

## Anti-Patterns

- Local success substituted for evidence of the concurrency control contract.

## Stop Conditions

Escalate when money, inventory, permissions, quotas, or cross-service reservations can violate an invariant, a distributed lease lacks fencing, or recovery is unproven.

## Output Contract

- concurrency plan with critical sections locks conflicts and tests, evidence, and proof limits

## Targeted References

| Path | Type | Load when | Do not load when | Required by | Required output |
|---|---|---|---|---|---|
| [benchmarks and patterns](references/benchmarks-and-patterns.md) | benchmark-pattern | Lost updates, stale ownership, deadlocks, or contention need mechanism selection | No overlapping actor can mutate the affected invariant | analysis-agent, task-agent, review-agent | option-comparison, selected-approach |
| [checklist](references/checklist.md) | decision-checklist | Concurrency spans retries, cancellation or timeout, lease ownership or another time-derived ownership claim, lock order, version reuse or ABA, duplicate effects, or scheduling fairness | The resource has one serialized owner | analysis-agent, task-agent, review-agent | checklist-result, residual-risk |
| [evidence patterns](references/evidence-patterns.md) | evidence-pattern | Safety claims require synchronized overlap or contention artifacts | No interleaving or ownership claim awaits proof | analysis-agent, task-agent, review-agent | evidence-record, proof-limit, residual-risk |

Files in this skill

  • SKILL.md3.1 KB
  • examples/example-output.md551 B
  • references/benchmarks-and-patterns.md5 KB
  • references/checklist.md2.4 KB
  • references/evidence-patterns.md1.6 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…