m07-concurrency
Skill14 starsChanged 9 months agoMITView on GitHub
Mastering C++ Concurrency. Triggers: std::thread, jthread, atomic, mutex, deadlock, race condition, memory model, coroutine, async.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- TeddyAlbina/skillstheir own version, first seen Nov 1, 2026
- moeru-ai/auvtheir own version, first seen Oct 10, 2026
- fjrevoredo/mini-diariumtheir own version, first seen Oct 8, 2026
- ZhangHanDong/rust-skillstheir own version, first seen Oct 8, 2026
- MovGP0/Skillstheir own version, first seen Jun 30, 2026
- pocket-veto/pocket-vetotheir own version, first seen Jun 27, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- ZhangHanDong/rust-skills★ 1.5ksame name
- actionbook/rust-skills★ 1.5ksame name
- fjrevoredo/mini-diarium★ 318same name
- moeru-ai/auv★ 207same name
- TeddyAlbina/skills★ 2same name
- MovGP0/Skills★ 1same name
- pocket-veto/pocket-veto★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- cpp20-skill-creatorSkill
- m01-ownershipSkill
- m02-resourceSkill
- m03-mutabilitySkill
- m04-zero-costSkill
- m05-type-drivenSkill
- m06-error-handlingSkill
- m09-domainSkill
- m10-performanceSkill
- m11-ecosystemSkill
- m12-lifecycleSkill
- m13-domain-errorSkill
- m14-mental-modelSkill
- m15-anti-patternSkill
The file
Files
C++ Concurrency
Core Question
How do threads communicate?
- Shared State: Mutexes (
std::mutex) or Atomics (std::atomic). - Coordination: Condition Variables (
std::condition_variable) or Latches/Semaphores (C++20). - Tasks:
std::asyncor Coroutines (C++20).
Error → Design Question
| Issue | Design Question |
| Data Race | Are two threads accessing memory without a Happens-Before edge? |
| Deadlock | Did you lock Mutex A then B, while another thread locked B then A? |
| False Sharing | Are independent atomics sitting on the same cache line? |
| Live Lock | Are threads spinning without progress? |
Thinking Prompt
- Do I need a thread?
- Short task? →
std::asyncor Thread Pool. - Long background? →
std::jthread.
- Short task? →
- Is it shared state?
- Yes? → Protect with
std::mutex. - Is it small/primitive? →
std::atomic.
- Yes? → Protect with
- Locks or Atomics?
- Logic requiring multiple steps? → Mutex (Atomic is only for single instructions).
- Simple flag/counter? → Atomic.
Trace Up / Down
- Trace Up:
- Issue: "Random update values in counter."
- Cause:
counter++is Read-Modify-Write, not atomic. Data race. - Fix:
std::atomic<int>.
Quick Reference
| Tool | C++ Version | Use When |
std::jthread | C++20 | Standard thread (auto-join). |
std::atomic | C++11 | Lock-free counters/flags. |
std::mutex | C++11 | Locking critical sections. |
std::shared_mutex | C++17 | Read-heavy workloads. |
std::latch | C++20 | Waiting for N tasks to start. |
co_await | C++20 | Async I/O (requires library). |
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.