sync-project
Skill2 starsChanged 2 months agoMITView on GitHub
Fetch, prune, and report status across one repo or a multi-repo umbrella while preserving dirty trees and surfacing divergence instead of silently resetting anything.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- MusserLab/lab-claude-skillstheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- MusserLab/lab-claude-skills★ 4same 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 repository19 other files it gives its agents.
- access-checkSkill
- babysit-prsSkill
- browser-proofSkill
- bugfixSkill
- bug-reproSkill
- cleanupSkill
- contextSkill
- dev-flowSkill
- docs-managerSkill
- hot-reloadSkill
- jira-managerSkill
- polishSkill
- pr-managerSkill
- release-proofSkill
- status-reportSkill
- watch-loopSkill
- whatsapp-meSkill
- workflowSkill
- worktreeSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
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 when a project or umbrella workspace needs a clean read on branch state before planning, implementation, or reporting.
- Distinctive: line 29
check whether the tree is clean or dirty
- Distinctive: line 52
Never reset a dirty tree.
- Distinctive: line 53
Never switch branches just to make the report look clean.
- Distinctive: line 55
If a repo has no upstream or no remote, say so plainly.
- Distinctive: line 68
every repo in scope has a fresh remote view and status report
≈ “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 Project
Use this when a project or umbrella workspace needs a clean read on branch state before planning, implementation, or reporting.
Goal
Bring remote knowledge up to date without disturbing local work.
Safe default actions
- fetch remotes
- prune stale remote references
- inspect branch state
- report divergence
- report dirty worktrees
This skill does not reset, discard, rebase, or rewrite local work by default.
Workflow
For each repo in scope:
- detect the current branch
- check whether the tree is clean or dirty
- fetch from the configured remote
- prune stale remote references if safe
- compare local branch, upstream branch, and merge base
- report divergence and blocked states
Output
Return one compact block per repo:
Repo:
Current branch:
Dirty:
Upstream:
Ahead/behind:
Diverged:
Open blocker:
Next safe action:Rules
- Never reset a dirty tree.
- Never switch branches just to make the report look clean.
- Never hide divergence.
- If a repo has no upstream or no remote, say so plainly.
- Preserve user worktrees and uncommitted work.
Good use
- sync before cutting a worktree
- sync before planning a feature
- sync an umbrella project before a daily report
Stop rules
Stop when:
- every repo in scope has a fresh remote view and status report
- a repo is blocked by auth or a dirty-tree condition that needs human judgment
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.

