Agent 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.

Stars 183,714
Forks 39,125

Install this agent skill to your Project

npx add-skill https://github.com/microsoft/vscode/tree/main/src/vs/sessions/skills/sync-upstream

SKILL.md

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.

Expand your agent's capabilities with these related and highly-rated skills.

microsoft/vscode

component-fixtures

Use when creating or updating component fixtures for screenshot testing, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, and common pitfalls.

183,714 39,125
Explore
microsoft/vscode

memory-leak-audit

Audit code for memory leaks and disposable issues. Use when reviewing event listeners, DOM handlers, lifecycle callbacks, or fixing leak reports. Covers addDisposableListener, Event.once, MutableDisposable, DisposableStore, and onWillDispose patterns.

183,714 39,125
Explore
microsoft/vscode

fix-ci-failures

Investigate and fix CI failures on a pull request. Use when CI checks fail on a PR branch — covers finding the PR, identifying failed checks, downloading logs and artifacts, extracting the failure cause, and iterating on a fix. Requires the `gh` CLI.

183,714 39,125
Explore
microsoft/vscode

azure-pipelines

Use when validating Azure DevOps pipeline changes for the VS Code build. Covers queueing builds, checking build status, viewing logs, and iterating on pipeline YAML changes without waiting for full CI runs.

183,714 39,125
Explore
microsoft/vscode

add-policy

Use when adding, modifying, or reviewing VS Code configuration policies. Covers the full policy lifecycle from registration to export to platform-specific artifacts. Run on ANY change that adds a `policy:` field to a configuration property.

183,714 39,125
Explore
microsoft/vscode

chat-customizations-editor

Use when working on the Chat Customizations editor — the management UI for agents, skills, instructions, hooks, prompts, MCP servers, and plugins.

183,714 39,125
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results