[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699DJMR6CE1MH5XCJZ0GFQ0":3,"skill-same:01M699DJMR6CE1MH5XCJZ0GFQ0":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":44,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M699DJMR6CE1MH5XCJZ0GFQ0","sync",null,"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.","microsoft\u002Fvscode","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M6998NK2WED5M549DX06VBCH",195270,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fsync\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"pull","push","publish","SET","rebase","branch","user","session","use","upstream","remote","with","latest","changes","when","2026-11-10 10:12:30",false,"---\nname: sync\ndescription: 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.\n---\n\u003C!-- Customize this skill and select save to override its behavior. Delete that copy to restore the built-in behavior. -->\n\n# Sync Changes\n\nSync 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.\n\n## Guidelines\n\n- **Never force-push** (`--force`, `--force-with-lease`) without explicit user approval.\n- **Never skip pre-push hooks** (do not use `--no-verify`).\n- **Never rewrite or drop commits** during rebase without asking the user.\n- When in doubt about conflict resolution — ask the user.\n\n## Workflow\n\n1. Check for uncommitted changes first. If there are uncommitted changes, use the `\u002Fcommit` skill to commit them before continuing.\n2. Check whether the current session branch has an upstream branch.\n3. If the current session branch has an upstream branch:\n   3.1. Fetch the upstream remote first so tracking refs are up to date.\n      ```\n      git fetch \u003Cupstream-remote>\n      ```\n   3.2. Check ahead\u002Fbehind counts. If the branch is already in sync (0 ahead, 0 behind), stop and report that no sync is needed.\n      ```\n      git rev-list --left-right --count HEAD...@{u}\n      ```\n   3.3. If behind, rebase onto the upstream tracking branch.\n      ```\n      git rebase @{u}\n      ```\n   3.4. If there are merge conflicts, resolve them by preserving the intent of both sides. Stage the resolved files and continue the rebase.\n      ```\n      git add \u003Cresolved-files>\n      git rebase --continue\n      ```\n      If conflict resolution is unclear, ask the user how to proceed. If the user wants to stop the rebase, abort it:\n      ```\n      git rebase --abort\n      ```\n   3.5. If the branch has local commits (ahead > 0), push them to the remote after a successful rebase.\n      ```\n      git push\n      ```\n      If the push is rejected because the rebase rewrote history, explain the situation to the user and ask for approval before force-pushing.\n4. If the current session branch does not have an upstream branch:\n   4.1. Determine the remote to publish to.\n      - If there is only one remote, use it.\n      - If there are multiple remotes, use the #tool:vscode\u002FaskQuestions tool to ask which remote to use.\n   4.2. Publish the current branch and set upstream in one step.\n      ```\n      git push -u \u003Cremote> HEAD\n      ```\n\n## Validation\n\nAfter the workflow completes, validate the result with explicit checks:\n\n1. Verify the working tree is clean:\n   ```\n   git status --porcelain\n   ```\n2. Verify sync state (ahead\u002Fbehind counts are both 0):\n   ```\n   git rev-list --left-right --count HEAD...@{u}\n   ```\n3. If the branch was newly published, verify the upstream branch is configured:\n   ```\n   git rev-parse --abbrev-ref --symbolic-full-name @{u}\n   ```\n","\u003C!-- Customize this skill and select save to override its behavior. Delete that copy to restore the built-in behavior. -->\n\n# Sync Changes\n\nSync 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.\n\n## Guidelines\n\n- **Never force-push** (`--force`, `--force-with-lease`) without explicit user approval.\n- **Never skip pre-push hooks** (do not use `--no-verify`).\n- **Never rewrite or drop commits** during rebase without asking the user.\n- When in doubt about conflict resolution — ask the user.\n\n## Workflow\n\n1. Check for uncommitted changes first. If there are uncommitted changes, use the `\u002Fcommit` skill to commit them before continuing.\n2. Check whether the current session branch has an upstream branch.\n3. If the current session branch has an upstream branch:\n   3.1. Fetch the upstream remote first so tracking refs are up to date.\n      ```\n      git fetch \u003Cupstream-remote>\n      ```\n   3.2. Check ahead\u002Fbehind counts. If the branch is already in sync (0 ahead, 0 behind), stop and report that no sync is needed.\n      ```\n      git rev-list --left-right --count HEAD...@{u}\n      ```\n   3.3. If behind, rebase onto the upstream tracking branch.\n      ```\n      git rebase @{u}\n      ```\n   3.4. If there are merge conflicts, resolve them by preserving the intent of both sides. Stage the resolved files and continue the rebase.\n      ```\n      git add \u003Cresolved-files>\n      git rebase --continue\n      ```\n      If conflict resolution is unclear, ask the user how to proceed. If the user wants to stop the rebase, abort it:\n      ```\n      git rebase --abort\n      ```\n   3.5. If the branch has local commits (ahead > 0), push them to the remote after a successful rebase.\n      ```\n      git push\n      ```\n      If the push is rejected because the rebase rewrote history, explain the situation to the user and ask for approval before force-pushing.\n4. If the current session branch does not have an upstream branch:\n   4.1. Determine the remote to publish to.\n      - If there is only one remote, use it.\n      - If there are multiple remotes, use the #tool:vscode\u002FaskQuestions tool to ask which remote to use.\n   4.2. Publish the current branch and set upstream in one step.\n      ```\n      git push -u \u003Cremote> HEAD\n      ```\n\n## Validation\n\nAfter the workflow completes, validate the result with explicit checks:\n\n1. Verify the working tree is clean:\n   ```\n   git status --porcelain\n   ```\n2. Verify sync state (ahead\u002Fbehind counts are both 0):\n   ```\n   git rev-list --left-right --count HEAD...@{u}\n   ```\n3. If the branch was newly published, verify the upstream branch is configured:\n   ```\n   git rev-parse --abbrev-ref --symbolic-full-name @{u}\n   ```\n",{"name":5,"description":7},"main","11ba54a90a0ff8720cf47c086f5a9948eef9cf2c","src\u002Fvs\u002Fsessions\u002Fskills\u002Fsync",43791,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode","https:\u002F\u002Fcode.visualstudio.com","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-12 03:13:10",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add microsoft\u002Fvscode --skill sync",{"tool":55,"command":56},"bunx","bunx skills add microsoft\u002Fvscode --skill sync",{"tool":58,"command":59},"pnpm","pnpm dlx skills add microsoft\u002Fvscode --skill sync","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fsync\u002FSKILL.md",true,[],[64,90,110,121,137,146],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":34},"01M70H0ANBKZAVEP1NVV4K28M3","sweeper-query","Answer natural-language questions about the VS Code Sweeper's published issue index (index-\u003Cname>.json for microsoft\u002Fvscode and the enrolled family repos) — which issues are agent-ready to implement or plan, what the sweeper proposed for an assignee or area, whether the sweeper knows a report as a duplicate, the highest-value open bugs in a lane — and, for one issue, the review's full record (evidence with file citations, fix brief, proposed comment). Use ONLY when the request explicitly names the sweeper — \"sweeper\", \"vscodesweeper\", \"sweeper-query\", a sweeper verdict, record, brief or index, an agent-ready issue — or asks what \"the sweeper\" found, proposed or knows. Do NOT use for general questions about issues, duplicates, priorities or ranking that do not mention the sweeper. Read-only; discovery only.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fsweeper-query\u002FSKILL.md",[],[71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,33,89],"sweeper query","query","sweeper","plan","natural-language","ranking","request","duplicates","ready","only","fix","read","which","open","Citations","brief","issues","code","review",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":34},"01M699DRJS4YJCV600Q72SVVWE","update-skills","Create or update repository skills and instructions when major learnings are discovered during a session. Use when the user says \"learn!\", when a significant pattern or pitfall is identified, or when reusable domain knowledge should be captured for future sessions.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fupdate-skills\u002FSKILL.md",[],[97,98,99,100,101,102,103,104,27,26,25,105,33,106,107,108,109],"update","update skills","knowledge","for","pattern","domain","learnings","reusable","instructions","repository","learn","create","sessions",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":34},"01M699DPWHZ72B66P82EW31RNE","update-pr","Update the pull request for the current session. Use when the user wants to push new changes to an existing PR.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fupdate-pr\u002FSKILL.md",[],[97,117,118,119,33,32,100,27,26,25,20,19,120,77],"pr","update pr","Existing","pull request",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":34},"01M699DGXHX6A2A72X57R6GGHJ","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.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fsync-upstream\u002FSKILL.md",[],[28,5,128,129,130,27,26,24,131,97,132,33,133,134,32,31,135,136],"sync upstream","stale","up","work","conflicts","catch","catch up","fit","origin",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":34},"01M699DEXYFWDGW0BAXJ5QQ377","merge","Merge changes from the topic branch to the merge base branch. Use when the user wants to merge their session's work back to the base branch.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fmerge\u002FSKILL.md",[],[139,33,32,144,145,27,26,25,24,131],"base","back",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":34},"01M699DD3FAAGVF9XBH1B2SJNY","generate-run-commands","Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fgenerate-run-commands\u002FSKILL.md",[],[153,154,155,156,22,25,97,100,33,27,26,130],"generate","generate run commands","commands","run"]