sync-upstream
Skill0 starsChanged 56 days agoMITView on GitHub
Update a stale session branch by rebasing onto the latest origin. Use when the upstream has moved significantly and the session needs to catch up, resolving conflicts by preserving upstream changes and adapting session work to fit.
16 other projects use a version of this.
Adopted by
Most recently taken up by
- Trixx4191/asrartheir own version, first seen Nov 15, 2026
- garfiec/Librechat-Mobiletheir own version, first seen Nov 11, 2026
- next-step/nextstep-skillstheir own version, first seen Nov 8, 2026
- parkchu/nextstep-claude-skillstheir own version, first seen Nov 1, 2026
- parkchu/nextstep-skillstheir own version, first seen Oct 17, 2026
- microsoft/vscodeword for word, first seen Oct 13, 2026
Used with
Projects with it also use start-mission, tdd and 1 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.
parkchuSkillstart-mission
넥스트스텝(NextStep) 미션을 처음 시작할 때, 미션 저장소를 fork·clone하고 최초 작업 브랜치(step1 등)까지 만들어 준다. gh CLI로 fork하고 clone까지 이어서 처리하며, gh가 없거나 인증이 안 돼 있으면 브라우저 Fork 안내로 폴백한다. 이미 fork/clone돼 있으면 재사용하고 이어서 진행한다(재실행 안전). 사용자가 "미션 시작하려는데 저장소 세팅해줘", "새 미션 시작할래", "fork부터 해줘", "/nextstep:start-mission" 등으로 요청할 때 사용한다.
Also in 3 projects that use this
GoogleSkilltdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Also in 3 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
Other versions16 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 · 14
- nyaruka/phonenumbers★ 1.6ksame name
- garfiec/Librechat-Mobile★ 160same name
- nklisch/claude-code-modes★ 116same name
- ric03uec/clawrium★ 67same name
- leandrocfe/skills★ 31same name
- tigercosmos/code-cortex-mcp★ 12same name
- freskhu/genesis★ 5same name
- lucasheriques/pstack★ 3same name
- toverux/cantrips★ 3same name
- Trixx4191/asrar★ 2same name
4 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
- syncSkill
- theme-factorySkill
- toolsSkill
- troubleshootSkill
- ui-ux-pro-maxSkill
- update-prSkill
- update-skillsSkill
- web-design-engineerSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
4
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
- Very specific: line 13
If there are uncommitted changes, use the /commit skill to commit them first.
- Distinctive: line 19
Use the appropriate base branch if it is not main.
- Distinctive: line 23
When conflicts arise, upstream always wins:
- Distinctive: line 27
After resolving each conflict, git add the files and git rebase --continue.
- Distinctive: line 31
After the rebase completes, verify the result still compiles and meets the session's objectives.
“Common” is measured: kept by at least 6 in 10 of the 9 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. -->Update Branch
Rebase the current session branch onto the latest upstream so the work stays grounded in origin.
Workflow
- If there are uncommitted changes, use the
/commitskill to commit them first. - Fetch the latest upstream and rebase onto it:
Use the appropriate base branch if it is notgit fetch origin git rebase origin/mainmain.
Conflict Resolution
When conflicts arise, upstream always wins:
- Never alter upstream logic, APIs, or patterns to accommodate session changes.
- Adapt session work to fit the new upstream — rename, restructure, or rewrite as needed while preserving the session's goals.
- After resolving each conflict,
git addthe files andgit rebase --continue.
Validation
After the rebase completes, verify the result still compiles and meets the session's objectives. If session changes no longer make sense against the updated upstream, explain what changed and propose a revised approach.
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.

