AGENT SKILL

update-instructions

update-instructions

License 许可
MIT
所属仓库
microsoft/vscode
最近更新
2026-11-13
Stars
★ 20w
Forks
4.4w

01 前言 Front Matter

name
update-instructions
description
update-instructions
disable-model-invocation
true

02 资源文件 1

03 SKILL.md 正文

Read the changes introduced on the current branch, including BOTH:

  1. Uncommitted workspace modifications (staged and unstaged)
  2. Committed changes that are on the current HEAD but not yet in the default upstream branch (e.g. origin/main)

Guidance:

  • First, capture uncommitted diffs (equivalent of git diff and git diff --cached).
  • Then, determine the merge base with the default branch (assume origin/main unless configured otherwise) using git merge-base HEAD origin/main and diff (git diff <merge-base>...HEAD) to include committed-but-unpushed work.

After understanding all of these changes, read every instruction file under .github/instructions and assess whether any instruction is invalidated. If so, propose minimal, necessary wording updates. If no updates are needed, respond exactly with: No updates needed.

Be concise and conservative: only suggest changes that are absolutely necessary.

04 同仓库更多 Skills

microsoft
microsoft/vscode

sweeper-query

Answer natural-language questions about the VS Code Sweeper's published issue index (index-<name>.json for microsoft/vscode 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.

★ 20w
microsoft
microsoft/vscode

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.

★ 20w
microsoft
microsoft/vscode

update-pr

Update the pull request for the current session. Use when the user wants to push new changes to an existing PR.

★ 20w
microsoft
microsoft/vscode

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.

★ 20w
microsoft
microsoft/vscode

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.

★ 20w
microsoft
microsoft/vscode

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.

★ 20w