Sync Upstream logo

Sync Upstream

OrganizationPopular
microsoft
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.

Overview

Publishermicrosoft
Repositoryvscode
Skill namesync-upstream
Stars
192.7K
Forks
42.7K
Bundled files
Instructions only
LicenseMIT
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by microsoft on GitHub. Read the source before you install it.

Installation

Install the Sync Upstream AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/microsoft/vscode.git /tmp/vscode
mkdir -p .claude/skills
cp -r /tmp/vscode/src/vs/sessions/skills/sync-upstream .claude/skills/sync-upstream
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Sync Upstream in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Sync Upstream on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Sync Upstream is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.

Frequently asked questions

What does the Sync Upstream AI skill do?

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.

Why use Sync Upstream on TypingMind?

Because you install it once and use it with any model. Sync Upstream is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Sync Upstream in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/microsoft/vscode/tree/main/src/vs/sessions/skills/sync-upstream. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Sync Upstream?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Sync Upstream?

As many as you like. As long as a model supports skills, you can use Sync Upstream with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Sync Upstream AI skill free?

Yes. It is published on GitHub by microsoft under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
mattpocock logo

Prototype

mattpocock
CommunityPopular

Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

22.3K
264.4K
3 files
View
mattpocock logo

Research

mattpocock
CommunityPopular

Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading…

22.3K
264.4K
1 files
View
mattpocock logo

Resolving Merge Conflicts

mattpocock
CommunityPopular

Use when you need to resolve an in-progress git merge/rebase conflict.

22.3K
264.4K
1 files
View
mattpocock logo

Setup Matt Pocock Skills

mattpocock
CommunityPopular

Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

22.3K
264.4K
6 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇