sync-conflict-playbook
Skill1 starsChanged 9 months agoMITView on GitHub
Define deterministic conflict resolution for offline/replicated state, including merge semantics and user-visible resolution flows.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- chaos-fuzz-runnerSkill
- data-migration-safetySkill
- external-integration-reliabilitySkill
- failure-forensicsSkill
- harmonization-operatorSkill
- hud-control-opsSkill
- mcp-policy-opsSkill
- search-index-tuningSkill
- smoke-gate-runnerSkill
- track-contract-authorSkill
- transaction-concurrency-guardSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when state can diverge across clients or replicas.
- Distinctive: line 21
Add conflict UX contract:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Sync Conflict Playbook
Use this skill when state can diverge across clients or replicas.
Workflow
- Classify entities by merge strategy:
- last-write-wins safe
- field-level merge
- manual resolution required
- Define conflict metadata contract:
- version/vector clock/revision token
- author/source timestamp
- causal ordering hints
- Specify server truth and client reconciliation loop.
- Add conflict UX contract:
- how conflict is surfaced
- safe default action
- user override path
Failure Modes To Handle
- Silent overwrite of user edits.
- Non-deterministic merge across clients.
- Infinite retry/replay loops on stale revisions.
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.