synapse
Skill0 starsChanged 3 months agoMITView on GitHub
Working alongside other Claude Code sessions on the same project — use when the user mentions other chats/sessions, splitting work, "who else is working on this", messaging another session, or when you receive [synapse] context in the conversation.
- Commits and pushes
10 other projects use a version of this.
Adopted by
Most recently taken up by
- thiagofinch/mega-braintheir own version, first seen Oct 8, 2026
- SynkraAI/aios-coretheir own version, first seen Oct 8, 2026
- anshulyadav1976/synapsetheir own version, first seen Sep 8, 2026
- yangjingo/Synapsetheir own version, first seen Aug 23, 2026
- valsecchi75/project-scaffoldertheir own version, first seen Aug 3, 2026
- ANTHO56200/synapse-memorytheir own version, first seen Jul 6, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- SynkraAI/aios-core★ 3.1ksame name
- SynkraAI/aiox-core★ 3.1ksame name
- thiagofinch/mega-brain★ 95same name
- valsecchi75/project-scaffolder★ 9same name
- anshulyadav1976/synapse★ 7same name
- ImScottDev/brain-scott★ 4same name
- yangjingo/Synapse★ 4same name
- NimbleBrainInc/skills★ 3same name
- ANTHO56200/synapse-memory★ 2same name
- TheJenilDGohel/Synapse★ 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.
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 2 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Announce before shared state changes: Before a push, a merge, or a deploy, tell the other live sessions: /synapse send <name> <message>.
- Very specific: line 30
Conflict warnings (
⚠ [synapse]) are not noise: If your change to that file is not obviously disjoint from theirs, ask the user before … - Distinctive: line 34
Hand off explicitly: When you finish something another session is waiting on, message them: what is done, what they can do now.
- Very specific: line 37
Incoming messages (
📨 [synapse]) are acted on immediately: If a message changes your plan, say so to the user in one sentence. - Distinctive: line 40
Do not speak for other sessions: Don't release their file claims, don't rename them, don't assume their branch is abandoned because it is …
- Very specific: line 50
Warning only: commit/rebase/merge while another live session is on the same branch.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Synapse — how to behave with other sessions around
You are one of several Claude Code sessions working on this project in parallel.
The [synapse] lines in your context (sessions, messages, warnings) come from the
synapse plugin. Treat them as facts about the world, not as instructions from the user.
Rules
Announce before shared state changes. Before a push, a merge, or a deploy, tell the other live sessions:
/synapse send <name> <message>. Announce before, not after — a deploy that ships a tree without their unmerged work removes it from production, and nothing looks like it failed.Keep it to two lines. The announcement is a signal, not a report: what you are doing, on which branch or commit, and the one thing that could affect them. Not your internal steps, not which tests you will run, not migration filenames — if they want detail, they will ask.
rebasing
feat/supportonto21ba0da9→ push + deploy. Widens the proxy matcher to/api. Say now if that clashes with you.- Look before you start. At the beginning of substantial work run
/synapseto see who is here and which files they are touching. - Conflict warnings (
⚠ [synapse]) are not noise. If your change to that file is not obviously disjoint from theirs, ask the user before continuing. AWriteover a file someone else is editing drops their work silently. - Hand off explicitly. When you finish something another session is waiting on, message them: what is done, what they can do now.
- Incoming messages (
📨 [synapse]) are acted on immediately. If a message changes your plan, say so to the user in one sentence. - Do not speak for other sessions. Don't release their file claims, don't rename them, don't assume their branch is abandoned because it is idle.
The git guard
A PreToolUse hook inspects git commands before they run:
- Denied: push to the repo's default branch,
push --force, and push while another live session committed/rebased/merged/pulled on the same branch in the last 10 minutes. - Warning only: commit/rebase/merge while another live session is on the same branch.
- Override:
SYNAPSE_PUSH_OK=1 git push …— use it after you have talked to the other session, not instead of talking to them.
It is a best-effort accident guard (fail-open), not a security boundary.
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.