Agent Skills
› sediman-agent/OpenSkynet
› principle-separate-before-serializing-shared-state
principle-separate-before-serializing-shared-state
GitHub指导在并发场景下处理共享可变状态。优先消除不必要的共享，让各Actor独立写入；仅在共享为必要前提时，通过锁文件或原子操作进行结构化串行化，避免竞态条件。
Trigger Scenarios
多个并发实体可能写入同一文件、分支或状态对象
需要设计并发安全的数据持久化策略
Install
npx skills add sediman-agent/OpenSkynet --skill principle-separate-before-serializing-shared-state -g -y
SKILL.md
Frontmatter
{
"name": "principle-separate-before-serializing-shared-state",
"description": "Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.",
"disable-model-invocation": true
}
Separate Before Serializing Shared State
When concurrent actors might share mutable state, first ask whether they truly need the same mutable object. If not, eliminate the sharing. When sharing is real, enforce serialization structurally: lockfiles, sequential phases, exclusive ownership. Instructions and conventions are not concurrency control.
Why: Concurrent writes to shared state create race conditions that are intermittent, hard to reproduce, and expensive to debug. Telling agents or goroutines to "take turns" does not work.
Pattern:
- Identify shared mutable state (files both read and write, branches both push to, APIs both define and consume).
- Default: eliminate the shared write target. Ask: do these actors need one canonical object, or are they publishing independent facts? Give each actor its own owned file, key, branch, or state directory, and merge only at the read/reporting boundary. Two workers writing their own
lastXfield into onestate.jsonis still shared mutation;indexer-state.json+metrics-state.jsonis not. - Only when one shared write target is a real invariant, serialize access structurally (lockfiles, sequential phases, single-writer actor, or atomic compare-and-swap). Treat "we need a lock" as a design smell to check, not as the default answer.
Version History
- c9d8953 Current 2026-07-05 19:53
