sync
Skill0 starsChanged 55 days agoMITView on GitHub
Sync the current session branch with its upstream branch, or publish the current session branch to a remote. Use when the user asks to sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream.
- Commits and pushes
57 other projects use a version of this.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- joryeugene/keephivetheir own version, first seen Nov 15, 2026
- muslim-sec/skillstheir own version, first seen Nov 15, 2026
- Trixx4191/asrartheir own version, first seen Nov 15, 2026
- grainulation/grainulatortheir own version, first seen Nov 12, 2026
- Catherine1401/agent-skillstheir own version, first seen Nov 8, 2026
- FabianoArthur/claude-code-kitchentheir own version, first seen Nov 8, 2026
Used with
Projects with it also use develop, scope and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
hong9LeeSkilldevelop
빌드, 아키텍처, git 관련 작업 시 OMS MSA 공통 인프라 규칙을 적용한다. 기술 스택, 빌드 명령, 헥사고날 아키텍처 구조, git 워크플로우, AI Context 동기화 규칙을 다룬다. 코드 작성 컨벤션은 /convention, 테스트 컨벤션은 /test-guide 스킬을 참조.
Also in 6 projects that use this
YuriNachosSkillscope
Configure claude-scope status line widgets for Claude Code. Use when user wants to customize widgets, change theme, reorder elements, or modify display style.
Also in 7 projects that use this
nicolasestremSkilldocument
Create focused documentation for specific components or features
Also in 5 projects that use this
kt057Skillcheck
lint, typecheck, test を一括実行して結果をサマリーする
Also in 6 projects that use this
Microsoft AzureSkilltest
Also in 8 projects that use this
Microsoft AzureSkillvalidate
Run the full CI validation workflow locally before submitting a PR. Use this as a final check to ensure all Azure DevOps CI pipeline steps will pass.
Also in 4 projects that use this
Other versions57 projects use a version of this.
Word for word · 2
- microsoft/vscode★ 195k100% same
- patterson-agents/skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 55
- jsmastery-pro/skills★ 1.4ksame name
- H-mmer/pentest-agents★ 815same name
- poingstudios/godot-admob-plugin★ 648same name
- cortex-tms/cortex-tms★ 180same name
- grainulation/grainulator★ 86same name
- lsnackerman/raw-clauding-skills★ 45same name
- fivetaku/tikeytaka★ 40same name
- namedtoaster/The-Last-Mile★ 39same name
- rlajous/claude-code-commands★ 30same name
- 5throck/ai-workspace-standards★ 25same name
45 more not listed
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 repository32 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- act-on-feedbackSkill
- algorithmic-artSkill
- animateSkill
- canvas-designSkill
- coderSkill
- code-reviewSkill
- coderSkill
- commitSkill
- create-draft-prSkill
- create-prSkill
- criticSkill
- designerSkill
- design-taste-frontendSkill
- fix-ciSkill
- frontend-designSkill
- generalistSkill
- generate-run-commandsSkill
- mergeSkill
- ponytailSkill
- researcherSkill
- researcherSkill
- securitySkill
- shadcnSkill
- sync-upstreamSkill
- theme-factorySkill
- toolsSkill
- troubleshootSkill
- ui-ux-pro-maxSkill
- update-prSkill
- update-skillsSkill
- web-design-engineerSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 12 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 47 edited versions we read keep these.
12
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
When in doubt about conflict resolution — ask the user.
- Very specific: line 20
Check for uncommitted changes first.
- Distinctive: line 21
Check whether the current session branch has an upstream branch.
- Distinctive: line 22
If the current session branch has an upstream branch: 3.1.
- Distinctive: line 40
If conflict resolution is unclear, ask the user how to proceed.
- Distinctive: line 48
If the push is rejected because the rebase rewrote history, explain the situation to the user and ask for approval before force-pushing.
- Distinctive: line 49
If the current session branch does not have an upstream branch: 4.1.
- Distinctive: line 51
If there is only one remote, use it.
- Distinctive: line 52
If there are multiple remotes, use the #tool:vscode/askQuestions tool to ask which remote to use.
- Distinctive: line 60
After the workflow completes, validate the result with explicit checks:
- Distinctive: line 62
Verify the working tree is clean:
- Distinctive: line 66
Verify sync state (ahead/behind counts are both 0):
- Distinctive: line 70
If the branch was newly published, verify the upstream branch is configured:
“Common” is measured: kept by at least 6 in 10 of the 47 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
<!-- Customize this skill and select save to override its behavior. Delete that copy to restore the built-in behavior. -->Sync Changes
Sync the current session branch with its upstream branch, or publish the current session branch to a remote. Use when the user asks to sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream.
Guidelines
- Never force-push (
--force,--force-with-lease) without explicit user approval. - Never skip pre-push hooks (do not use
--no-verify). - Never rewrite or drop commits during rebase without asking the user.
- When in doubt about conflict resolution — ask the user.
Workflow
- Check for uncommitted changes first. If there are uncommitted changes, use the
/commitskill to commit them before continuing. - Check whether the current session branch has an upstream branch.
- If the current session branch has an upstream branch:
3.1. Fetch the upstream remote first so tracking refs are up to date.
3.2. Check ahead/behind counts. If the branch is already in sync (0 ahead, 0 behind), stop and report that no sync is needed.git fetch <upstream-remote>
3.3. If behind, rebase onto the upstream tracking branch.git rev-list --left-right --count HEAD...@{u}
3.4. If there are merge conflicts, resolve them by preserving the intent of both sides. Stage the resolved files and continue the rebase.git rebase @{u}
If conflict resolution is unclear, ask the user how to proceed. If the user wants to stop the rebase, abort it:git add <resolved-files> git rebase --continue
3.5. If the branch has local commits (ahead > 0), push them to the remote after a successful rebase.git rebase --abort
If the push is rejected because the rebase rewrote history, explain the situation to the user and ask for approval before force-pushing.git push - If the current session branch does not have an upstream branch:
4.1. Determine the remote to publish to.
- If there is only one remote, use it.
- If there are multiple remotes, use the #tool:vscode/askQuestions tool to ask which remote to use. 4.2. Publish the current branch and set upstream in one step.
git push -u <remote> HEAD
Validation
After the workflow completes, validate the result with explicit checks:
- Verify the working tree is clean:
git status --porcelain - Verify sync state (ahead/behind counts are both 0):
git rev-list --left-right --count HEAD...@{u} - If the branch was newly published, verify the upstream branch is configured:
git rev-parse --abbrev-ref --symbolic-full-name @{u}
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.

