[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699DRJS4YJCV600Q72SVVWE":3,"skill-same:01M699DRJS4YJCV600Q72SVVWE":71},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M699DRJS4YJCV600Q72SVVWE","update-skills",null,"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.","microsoft\u002Fvscode","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M6998NK2WED5M549DX06VBCH",195271,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fupdate-skills\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"update skills","update","when","sessions","for","pattern","domain","learnings","reusable","use","session","user","instructions","knowledge","repository","learn","create","2026-11-10 10:12:30",false,"---\nname: update-skills\ndescription: 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.\n---\n\u003C!-- Customize this skill and select save to override its behavior. Delete that copy to restore the built-in behavior. -->\n\n# Update Skills & Instructions\n\nWhen a major repository learning is discovered — a recurring pattern, a non-obvious pitfall, a crucial architectural constraint, or domain knowledge that would save future sessions significant time — capture it as a skill or instruction so it persists across sessions.\n\n## When to Use\n\n- The user explicitly says **\"learn!\"** or asks to capture a learning\n- You discover a significant pattern or constraint that cost meaningful debugging time\n- You identify reusable domain knowledge that isn't documented anywhere in the repo\n- A correction from the user reveals a general principle worth preserving\n\n## Decision: Skill vs Instruction vs Learning\n\n**Add a learning to an existing instruction** when:\n- The insight is small (1-4 sentences) and fits naturally into an existing instruction file\n- It refines or extends an existing guideline\n- Follow the pattern in `.github\u002Finstructions\u002Flearnings.instructions.md`\n\n**Create or update a skill** (`.github\u002Fskills\u002F{name}\u002FSKILL.md` or `.agents\u002Fskills\u002F{name}\u002FSKILL.md`) when:\n- The knowledge is substantial (multi-step procedure, detailed guidelines, or rich examples)\n- It covers a distinct domain area (e.g., \"how to debug X\", \"patterns for Y\")\n- Future sessions should be able to invoke it by name\n\n**Create or update an instruction** (`.github\u002Finstructions\u002F{name}.instructions.md`) when:\n- The rule should apply automatically based on file patterns (`applyTo`) or globally\n- It's a coding convention, architectural constraint, or process rule\n- It doesn't need to be invoked on demand\n\n## Procedure\n\n### 1. Identify the Learning\n\nReflect on what went wrong or what was discovered:\n- What was the problem or unexpected behavior?\n- Why was it a problem? (root cause, not symptoms)\n- How was it fixed or what's the correct approach?\n- Can it be generalized beyond this specific instance?\n\n### 2. Check for Existing Files\n\nBefore creating new files, search for existing skills and instructions that might be the right home:\n\n```\n# Check existing skills\nls .github\u002Fskills\u002F .agents\u002Fskills\u002F 2>\u002Fdev\u002Fnull\n\n# Check existing instructions\nls .github\u002Finstructions\u002F 2>\u002Fdev\u002Fnull\n\n# Search for related content\ngrep -r \"related-keyword\" .github\u002Fskills\u002F .github\u002Finstructions\u002F .agents\u002Fskills\u002F\n```\n\n### 3a. Add to Existing File\n\nIf an appropriate file exists, add the learning to its `## Learnings` section (create the section if it doesn't exist). Each learning should be 1-4 sentences.\n\n### 3b. Create a New Skill\n\nIf the knowledge warrants a standalone skill:\n\n1. Choose the location:\n   - `.github\u002Fskills\u002F{name}\u002FSKILL.md` for project-level skills (committed to repo)\n   - `.agents\u002Fskills\u002F{name}\u002FSKILL.md` for agent-specific skills\n2. Create the directory and SKILL.md with frontmatter:\n\n```markdown\n---\nname: {skill-name}\ndescription: {One-line description of when and why to use this skill.}\n---\n\n# {Skill Title}\n\n{Body with guidelines, procedures, examples, and learnings.}\n```\n\n3. The `name` field **must match** the parent folder name exactly.\n4. Include concrete examples — skills with examples are far more useful than abstract rules.\n\n### 3c. Create a New Instruction\n\nIf the knowledge should apply automatically:\n\n```markdown\n---\ndescription: {When these instructions should be loaded}\napplyTo: '{glob pattern}' # optional — auto-load when matching files are attached\n---\n\n{Content of the instruction.}\n```\n\n### 4. Quality Checks\n\nBefore saving:\n- Is the learning **general enough** to help future sessions, not just this one?\n- Is it **specific enough** to be actionable, not just a vague principle?\n- Does it include a **concrete example** of right vs wrong?\n- Does it avoid duplicating knowledge already captured elsewhere?\n- Is the description clear enough that the agent will know **when** to invoke\u002Fapply it?\n\n### 5. Inform the User\n\nAfter creating or updating the file:\n- Summarize what was captured and where\n- Explain why this location was chosen\n- Note if any existing content was updated vs new content created\n","\u003C!-- Customize this skill and select save to override its behavior. Delete that copy to restore the built-in behavior. -->\n\n# Update Skills & Instructions\n\nWhen a major repository learning is discovered — a recurring pattern, a non-obvious pitfall, a crucial architectural constraint, or domain knowledge that would save future sessions significant time — capture it as a skill or instruction so it persists across sessions.\n\n## When to Use\n\n- The user explicitly says **\"learn!\"** or asks to capture a learning\n- You discover a significant pattern or constraint that cost meaningful debugging time\n- You identify reusable domain knowledge that isn't documented anywhere in the repo\n- A correction from the user reveals a general principle worth preserving\n\n## Decision: Skill vs Instruction vs Learning\n\n**Add a learning to an existing instruction** when:\n- The insight is small (1-4 sentences) and fits naturally into an existing instruction file\n- It refines or extends an existing guideline\n- Follow the pattern in `.github\u002Finstructions\u002Flearnings.instructions.md`\n\n**Create or update a skill** (`.github\u002Fskills\u002F{name}\u002FSKILL.md` or `.agents\u002Fskills\u002F{name}\u002FSKILL.md`) when:\n- The knowledge is substantial (multi-step procedure, detailed guidelines, or rich examples)\n- It covers a distinct domain area (e.g., \"how to debug X\", \"patterns for Y\")\n- Future sessions should be able to invoke it by name\n\n**Create or update an instruction** (`.github\u002Finstructions\u002F{name}.instructions.md`) when:\n- The rule should apply automatically based on file patterns (`applyTo`) or globally\n- It's a coding convention, architectural constraint, or process rule\n- It doesn't need to be invoked on demand\n\n## Procedure\n\n### 1. Identify the Learning\n\nReflect on what went wrong or what was discovered:\n- What was the problem or unexpected behavior?\n- Why was it a problem? (root cause, not symptoms)\n- How was it fixed or what's the correct approach?\n- Can it be generalized beyond this specific instance?\n\n### 2. Check for Existing Files\n\nBefore creating new files, search for existing skills and instructions that might be the right home:\n\n```\n# Check existing skills\nls .github\u002Fskills\u002F .agents\u002Fskills\u002F 2>\u002Fdev\u002Fnull\n\n# Check existing instructions\nls .github\u002Finstructions\u002F 2>\u002Fdev\u002Fnull\n\n# Search for related content\ngrep -r \"related-keyword\" .github\u002Fskills\u002F .github\u002Finstructions\u002F .agents\u002Fskills\u002F\n```\n\n### 3a. Add to Existing File\n\nIf an appropriate file exists, add the learning to its `## Learnings` section (create the section if it doesn't exist). Each learning should be 1-4 sentences.\n\n### 3b. Create a New Skill\n\nIf the knowledge warrants a standalone skill:\n\n1. Choose the location:\n   - `.github\u002Fskills\u002F{name}\u002FSKILL.md` for project-level skills (committed to repo)\n   - `.agents\u002Fskills\u002F{name}\u002FSKILL.md` for agent-specific skills\n2. Create the directory and SKILL.md with frontmatter:\n\n```markdown\n---\nname: {skill-name}\ndescription: {One-line description of when and why to use this skill.}\n---\n\n# {Skill Title}\n\n{Body with guidelines, procedures, examples, and learnings.}\n```\n\n3. The `name` field **must match** the parent folder name exactly.\n4. Include concrete examples — skills with examples are far more useful than abstract rules.\n\n### 3c. Create a New Instruction\n\nIf the knowledge should apply automatically:\n\n```markdown\n---\ndescription: {When these instructions should be loaded}\napplyTo: '{glob pattern}' # optional — auto-load when matching files are attached\n---\n\n{Content of the instruction.}\n```\n\n### 4. Quality Checks\n\nBefore saving:\n- Is the learning **general enough** to help future sessions, not just this one?\n- Is it **specific enough** to be actionable, not just a vague principle?\n- Does it include a **concrete example** of right vs wrong?\n- Does it avoid duplicating knowledge already captured elsewhere?\n- Is the description clear enough that the agent will know **when** to invoke\u002Fapply it?\n\n### 5. Inform the User\n\nAfter creating or updating the file:\n- Summarize what was captured and where\n- Explain why this location was chosen\n- Note if any existing content was updated vs new content created\n",{"name":5,"description":7},"main","11ba54a90a0ff8720cf47c086f5a9948eef9cf2c","src\u002Fvs\u002Fsessions\u002Fskills\u002Fupdate-skills",43773,"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-11 08:47:49",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add microsoft\u002Fvscode --skill update-skills",{"tool":57,"command":58},"bunx","bunx skills add microsoft\u002Fvscode --skill update-skills",{"tool":60,"command":61},"pnpm","pnpm dlx skills add microsoft\u002Fvscode --skill update-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fupdate-skills\u002FSKILL.md",true,[65],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"agents\u002Fopenai.yaml","REFERENCE","参考文档",145,"https:\u002F\u002Fgithub.com\u002Fnichee\u002Fdotfiles\u002Fblob\u002Fmain\u002Fclaude\u002Fskills\u002Fgrill-with-docs\u002Fagents\u002Fopenai.yaml",[72,98,112,127,143,152],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":36},"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",[],[79,80,81,82,21,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97],"sweeper query","query","sweeper","fix","request","which","natural-language","ranking","duplicates","ready","only","review","read","plan","open","Citations","brief","issues","code",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":36},"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",[],[20,105,106,107,21,83,108,109,23,28,29,30,110,111],"pr","update pr","pull","Existing","changes","push","pull request",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":36},"01M699DJMR6CE1MH5XCJZ0GFQ0","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.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fsync\u002FSKILL.md",[],[114,119,120,121,21,109,107,122,28,29,30,123,124,125,126,110],"latest","with","remote","upstream","branch","rebase","SET","publish",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":36},"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",[],[122,114,134,135,136,137,28,29,123,138,20,21,139,140,109,119,141,142],"sync upstream","conflicts","stale","up","work","catch","catch up","fit","origin",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":36},"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",[],[145,21,109,150,151,28,29,30,123,138],"base","back",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":36},"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",[],[159,160,161,162,125,30,29,20,23,137,21,28],"generate","generate run commands","commands","run"]