Agent skill · software engineering · microsoft
sync
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.
Why this skill is useful
Adds an executable script for syncing branches with upstream, including conflict resolution and validation steps that aren't in public docs.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 188,455 stars on the source repository.
What this skill does
<!-- 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 1. Check for uncommitted changes first. If there are uncommitted changes, use the /commit skill to commit them before continuing. 2. Check whether the current session branch has an upstream branch. 3. 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. 3.3. If behind, rebase onto the upstream tracking branch. 3.4. If there are merge conflicts, resolve them by preserving the intent of both sides. Stage the resolved files and continue the rebase. If conflict resolution is unclear, ask the user how to proceed. If the user wants to stop the rebase, abort it: 3.5. If the branch has local commits (ahead > 0), push them to the remote after a successful rebase. If the push is rejected because the rebase rewrote history, explain the situation to the user and ask for approval before force-pushing. 4. 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills microsoft/sync