Skip to content
Development
Skill

/sync-upstream

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.

From plugin
vscode
189k26 skills
Install
$ npx -y skills add microsoft/vscode --skill sync-upstream --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/sync-upstream

Context preview

The summary Claude sees to decide when to auto-load this skill.

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.

SKILL.md

sync-upstream.SKILL.md
name: sync-upstream
description: 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.

<!-- 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

1. If there are uncommitted changes, use the `/commit` skill to commit them first. 2. Fetch the latest upstream and rebase onto it:

   git fetch origin
   git rebase origin/main

Use the appropriate base branch if it is not `main`.

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 add` the files and `git 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.

Ships withvscode

Visual Studio Code

Get the whole plugin
Stats
188,564
Stars
41,520
Forks
Active
Maintenance
TypeScript
Language
MIT
License
48m ago
Last commit
10y ago
Created

Repo: microsoft/vscode