push-changes
Skill0 starsChanged 6 months agoLicence not identifiedView on GitHub
Commits and pushes the user's customizations in custom/ and overrides/ to their private synapse fork on GitHub. Trigger when the user says any of "push my synapse changes", "save my synapse work", "commit my synapse", "push omnipresence", "push my customizations", "save what I added to synapse". This is the ONE canonical save-and-push flow. Only commits files in custom/ and overrides/ - never touches core/, even if the user accidentally edited it. Safe to run after editing methodology / process / skill files in the member zones.
- Commits and pushes
1 other project uses a version of this.
Adopted by
Most recently taken up by
- torrust/torrust-trackertheir own version, first seen Nov 16, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- torrust/torrust-tracker★ 538same 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 repository23 other files it gives its agents.
- connect-dataforseoSkill
- connect-emailSkill
- connect-google-cloudSkill
- connect-openaiSkill
- continue-strategySkill
- create-workerSkill
- disconnect-dataforseoSkill
- disconnect-emailSkill
- disconnect-google-cloudSkill
- disconnect-openaiSkill
- domain-migration-checklistSkill
- fill-project-gapSkill
- getting-startedSkill
- list-projectsSkill
- list-strategiesSkill
- load-workerSkill
- new-projectSkill
- new-strategySkill
- project-infoSkill
- project-resolverSkill
- reload-workerSkill
- switch-projectSkill
- sync-omnipresenceSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 10 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
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.

