[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699BX77QFE0H5JJW9AY8RHZ":3,"skill-same:01M699BX77QFE0H5JJW9AY8RHZ":73},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M699BX77QFE0H5JJW9AY8RHZ","ux-theming",null,"VS Code theming, color tokens, widget styles, focus indicators, and high-contrast theme support. Use when registering colors, styling widgets with theme tokens, or ensuring HC\u002Ffocus compliance.","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\u002F.github\u002Fskills\u002Fux-theming\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"ux theming","ux","theming","when","support","high-contrast","hc","high","contrast","with","styles","theme","color","widgets","tokens","focus","use","indicators","compliance","code","2026-11-10 10:12:30",false,"---\nname: ux-theming\ndescription: VS Code theming, color tokens, widget styles, focus indicators, and high-contrast theme support. Use when registering colors, styling widgets with theme tokens, or ensuring HC\u002Ffocus compliance.\n---\n\nThis skill covers color registration, CSS variable usage, widget style patterns, focus indicators, and high-contrast theme requirements.\n\n---\n\n## 1. Registering Colors\n\n**File**: `src\u002Fvs\u002Fplatform\u002Ftheme\u002Fcommon\u002FcolorUtils.ts`\n\n```typescript\nexport const myWidgetBackground = registerColor('myWidget.background',\n    { light: '#ffffff', dark: '#252526', hcDark: Color.black, hcLight: Color.white },\n    nls.localize('myWidgetBackground', \"Background color of My Widget.\"));\n```\n\n**Rules**:\n- Provide defaults for all four theme types: `light`, `dark`, `hcDark`, `hcLight`.\n- HC themes must use solid colors (avoid transparency) and set explicit borders via `contrastBorder`.\n- Use color transforms for derived colors: `transparent()`, `darken()`, `lighten()`, `oneOf()`.\n- Reference existing colors when possible instead of hardcoding hex values.\n\n## 2. Color Categories\n\n| File | Colors |\n|------|--------|\n| `src\u002Fvs\u002Fplatform\u002Ftheme\u002Fcommon\u002Fcolors\u002FbaseColors.ts` | `foreground`, `focusBorder`, `contrastBorder`, text links |\n| `src\u002Fvs\u002Fplatform\u002Ftheme\u002Fcommon\u002Fcolors\u002FeditorColors.ts` | Editor widgets, find match, errors\u002Fwarnings |\n| `src\u002Fvs\u002Fplatform\u002Ftheme\u002Fcommon\u002Fcolors\u002FinputColors.ts` | Input, toggle, validation |\n| `src\u002Fvs\u002Fplatform\u002Ftheme\u002Fcommon\u002Fcolors\u002FlistColors.ts` | List\u002Ftree selection, focus, hover, drop |\n| `src\u002Fvs\u002Fplatform\u002Ftheme\u002Fcommon\u002Fcolors\u002FmiscColors.ts` | Badge, scrollbar, progress bar, sash |\n| `src\u002Fvs\u002Fworkbench\u002Fcommon\u002Ftheme.ts` | Tabs, sidebar, status bar, panels, editor groups, banner |\n\n## 3. Using Colors in CSS\n\nColors are injected as CSS custom properties on `.monaco-workbench`:\n\n```\nColor ID: editor.background\nCSS variable: --vscode-editor-background\nUsage: var(--vscode-editor-background)\n```\n\nConversion functions in `colorUtils.ts`:\n- `asCssVariable(colorId)` → `'var(--vscode-editor-background)'`\n- `asCssVariableName(colorId)` → `'--vscode-editor-background'`\n\n**In CSS files**, reference directly:\n```css\n.my-widget {\n    background-color: var(--vscode-editor-background);\n    color: var(--vscode-foreground);\n    border: 1px solid var(--vscode-contrastBorder);\n}\n```\n\nTrace the rendered control before choosing a token or selector; custom editor overlays may not use native input pseudo-elements. Inspect inherited and nested styles as well as the component's own declarations.\n\n### Contrast and Interaction States\n\n- Treat foreground and background as a semantic pair. A background change requires checking text, placeholders, links, operable inactive icons, hover, selection, and focus against the final composited surface.\n- Resolve defaults, opacity, and user overrides before measuring contrast. For example, an opaque icon color may meet contrast requirements while its translucent inactive variant does not.\n- Normal-size text and placeholders need at least 4.5:1 contrast; visual information needed to identify controls and focus needs at least 3:1 against adjacent colors. Apply the relevant accessibility criteria rather than extending these thresholds to decorative or disabled content. Unselected but operable controls are not disabled.\n- Check nested labels and descriptions in combined states; an explicit child foreground can defeat a correctly paired selection background.\n\n## 4. Widget Styles Pattern\n\n**File**: `src\u002Fvs\u002Fplatform\u002Ftheme\u002Fbrowser\u002FdefaultStyles.ts`\n\nEvery widget type has a default style object and an override factory:\n\n```typescript\n\u002F\u002F Use defaults:\nconst button = new Button(container, defaultButtonStyles);\n\n\u002F\u002F Override specific colors:\nconst button = new Button(container, getButtonStyles({\n    buttonBackground: myCustomBackgroundColor\n}));\n```\n\nAvailable defaults: `defaultButtonStyles`, `defaultInputBoxStyles`, `defaultCheckboxStyles`, `defaultToggleStyles`, `defaultDialogStyles`, `defaultListStyles`, `defaultSelectBoxStyles`, `defaultMenuStyles`, `defaultProgressBarStyles`, `defaultCountBadgeStyles`, `defaultBreadcrumbsWidgetStyles`, `defaultKeybindingLabelStyles`, `defaultFindWidgetStyles`.\n\n### Transient Theme Overrides\n\nUse the owning theme service for temporary palettes so CSS variables and programmatic color consumers remain consistent. Keep overrides scoped to the intended window and preserve the base theme and user customizations.\n\nVerify enabling, disabling, replacement, disposal, and theme changes, including stale asynchronous results. Clearing an override must restore the original colors without persisting generated values or changing another window's theme or startup colors.\n\n## 5. Focus Indicators\n\nDefined in `src\u002Fvs\u002Fworkbench\u002Fbrowser\u002Fmedia\u002Fstyle.css`:\n\n```css\n.my-widget:focus {\n    outline-width: 1px;\n    outline-style: solid;\n    outline-offset: -1px;\n    outline-color: var(--vscode-focusBorder);\n}\n```\n\n**Rules**:\n- Use `var(--vscode-focusBorder)` — never hardcode a focus color.\n- Default `outline-offset: -1px` (inset). Exception: checkboxes use `2px`.\n- Active elements suppress focus ring: `.my-widget:active { outline: 0 !important; }`\n- Use `.synthetic-focus` class for programmatic focus indication.\n- Toggle buttons use `border: 1px dashed var(--vscode-focusBorder)` instead of outline.\n- Check keyboard focus independently from selection and hover, including ordinary links without explicit `tabindex` and icon-only controls. Inspect computed outlines and pseudo-elements under production styles; token registration alone does not establish visibility.\n- Preserve a clear focus boundary through clipping and modal wrappers. Resolve competing border\u002Foutline ownership rather than adding duplicate rings or removing focus visibility.\n\n### Focus Trapping\n\nModal dialogs must trap focus within the dialog until dismissed. Use `dom.trackFocus()` and handle `Tab`\u002F`Shift+Tab` cycling.\n\n## 6. High Contrast Theme Rules\n\n- **Always** provide `hcDark` and `hcLight` defaults when registering colors.\n- HC backgrounds: `Color.black` (hcDark), `Color.white` (hcLight).\n- HC borders: reference `contrastBorder` — it is `null` in normal themes, visible in HC.\n- HC focus: use `activeContrastBorder` (derived from `focusBorder`).\n- In CSS, use `.hc-black` \u002F `.hc-light` class selectors for HC-specific overrides:\n  ```css\n  .hc-black .my-widget { border: 1px solid var(--vscode-contrastBorder); }\n  ```\n- In TypeScript, check `isHighContrast(theme.type)` for runtime behavior changes.\n- **Box shadows** must be removed or replaced in HC mode (shadows are invisible\u002Fdistracting with high contrast borders):\n  ```css\n  .my-widget {\n      box-shadow: 0 1px 3px var(--vscode-widget-shadow);\n  }\n  .vscode-high-contrast .my-widget {\n      box-shadow: none;\n      border: 1px solid var(--vscode-contrastBorder);\n  }\n  ```\n\nValidate both HC themes explicitly when changing borders, focus, or theme-dependent visibility; default dark\u002Flight screenshots do not cover them. Render through the production state-owning services so intentionally omitted decoration remains absent.\n\nTest runtime theme changes and custom color overrides, including transitions where a previously defined token becomes absent. Clear stale inline colors or classes rather than leaving the previous theme's state behind. Include competing workbench styles when inspecting the cascade.\n\n## 7. No Hardcoded Visual Values\n\nReviewers will always flag hardcoded colors, shadows, sizes that should use theme tokens or CSS variables.\n\n| Hardcoded (flagged) | Correct |\n|---------------------|---------|\n| `rgba(0, 0, 0, 0.12)` | `var(--vscode-widget-shadow)` or theme-aware variable |\n| `#252526` | `var(--vscode-editor-background)` |\n| `color: white` | `var(--vscode-button-foreground)` |\n| `border: 1px solid #ccc` | `var(--vscode-editorWidget-border)` |\n| `border: 1px solid …` (width) | `var(--vscode-strokeThickness)` for the 1px width |\n| `border-radius: 6px` | `var(--vscode-cornerRadius-medium)` (radius ramp) |\n| `padding: 8px 12px` (off-scale) | spacing ramp (`--vscode-spacing-size*`) |\n| `font-size: 14px` (arbitrary) | size ramp (`--vscode-fontSize-*`) |\n| `font-weight: 500` | `--vscode-fontWeight-semiBold` (no 500) |\n| codicon `font-size: 14px` | `--vscode-codiconFontSize` (16) \u002F `-compact` (12) |\n\n**Rule:** If a value relates to color, shadow, or border — it must come from a CSS variable or registered color token. The only exception is `0` (zero) values and purely structural measurements like `100%`.\n\n**Size, spacing, radius, font and stroke** values have their own design-system **size** tokens (and decision logic — snap maps, the pill→`circle` rule, and the compact-glyph convention). Those live in the **ux-css-layout** skill (§10 Design-System Size Tokens) and the auto-injected `.github\u002Finstructions\u002Fdesign-tokens.instructions.md`. Reach for those when a flag is about *how big \u002F how round \u002F how bold* something is rather than *what color*.\n\n---\n\n## Key Files\n\n| Area | File |\n|------|------|\n| Color registration | `src\u002Fvs\u002Fplatform\u002Ftheme\u002Fcommon\u002FcolorUtils.ts` |\n| Color registry (barrel) | `src\u002Fvs\u002Fplatform\u002Ftheme\u002Fcommon\u002FcolorRegistry.ts` |\n| Base colors | `src\u002Fvs\u002Fplatform\u002Ftheme\u002Fcommon\u002Fcolors\u002FbaseColors.ts` |\n| Workbench colors | `src\u002Fvs\u002Fworkbench\u002Fcommon\u002Ftheme.ts` |\n| Default widget styles | `src\u002Fvs\u002Fplatform\u002Ftheme\u002Fbrowser\u002FdefaultStyles.ts` |\n| Global workbench styles | `src\u002Fvs\u002Fworkbench\u002Fbrowser\u002Fmedia\u002Fstyle.css` |\n","This skill covers color registration, CSS variable usage, widget style patterns, focus indicators, and high-contrast theme requirements.\n\n---\n\n## 1. Registering Colors\n\n**File**: `src\u002Fvs\u002Fplatform\u002Ftheme\u002Fcommon\u002FcolorUtils.ts`\n\n```typescript\nexport const myWidgetBackground = registerColor('myWidget.background',\n    { light: '#ffffff', dark: '#252526', hcDark: Color.black, hcLight: Color.white },\n    nls.localize('myWidgetBackground', \"Background color of My Widget.\"));\n```\n\n**Rules**:\n- Provide defaults for all four theme types: `light`, `dark`, `hcDark`, `hcLight`.\n- HC themes must use solid colors (avoid transparency) and set explicit borders via `contrastBorder`.\n- Use color transforms for derived colors: `transparent()`, `darken()`, `lighten()`, `oneOf()`.\n- Reference existing colors when possible instead of hardcoding hex values.\n\n## 2. Color Categories\n\n| File | Colors |\n|------|--------|\n| `src\u002Fvs\u002Fplatform\u002Ftheme\u002Fcommon\u002Fcolors\u002FbaseColors.ts` | `foreground`, `focusBorder`, `contrastBorder`, text links |\n| `src\u002Fvs\u002Fplatform\u002Ftheme\u002Fcommon\u002Fcolors\u002FeditorColors.ts` | Editor widgets, find match, errors\u002Fwarnings |\n| `src\u002Fvs\u002Fplatform\u002Ftheme\u002Fcommon\u002Fcolors\u002FinputColors.ts` | Input, toggle, validation |\n| `src\u002Fvs\u002Fplatform\u002Ftheme\u002Fcommon\u002Fcolors\u002FlistColors.ts` | List\u002Ftree selection, focus, hover, drop |\n| `src\u002Fvs\u002Fplatform\u002Ftheme\u002Fcommon\u002Fcolors\u002FmiscColors.ts` | Badge, scrollbar, progress bar, sash |\n| `src\u002Fvs\u002Fworkbench\u002Fcommon\u002Ftheme.ts` | Tabs, sidebar, status bar, panels, editor groups, banner |\n\n## 3. Using Colors in CSS\n\nColors are injected as CSS custom properties on `.monaco-workbench`:\n\n```\nColor ID: editor.background\nCSS variable: --vscode-editor-background\nUsage: var(--vscode-editor-background)\n```\n\nConversion functions in `colorUtils.ts`:\n- `asCssVariable(colorId)` → `'var(--vscode-editor-background)'`\n- `asCssVariableName(colorId)` → `'--vscode-editor-background'`\n\n**In CSS files**, reference directly:\n```css\n.my-widget {\n    background-color: var(--vscode-editor-background);\n    color: var(--vscode-foreground);\n    border: 1px solid var(--vscode-contrastBorder);\n}\n```\n\nTrace the rendered control before choosing a token or selector; custom editor overlays may not use native input pseudo-elements. Inspect inherited and nested styles as well as the component's own declarations.\n\n### Contrast and Interaction States\n\n- Treat foreground and background as a semantic pair. A background change requires checking text, placeholders, links, operable inactive icons, hover, selection, and focus against the final composited surface.\n- Resolve defaults, opacity, and user overrides before measuring contrast. For example, an opaque icon color may meet contrast requirements while its translucent inactive variant does not.\n- Normal-size text and placeholders need at least 4.5:1 contrast; visual information needed to identify controls and focus needs at least 3:1 against adjacent colors. Apply the relevant accessibility criteria rather than extending these thresholds to decorative or disabled content. Unselected but operable controls are not disabled.\n- Check nested labels and descriptions in combined states; an explicit child foreground can defeat a correctly paired selection background.\n\n## 4. Widget Styles Pattern\n\n**File**: `src\u002Fvs\u002Fplatform\u002Ftheme\u002Fbrowser\u002FdefaultStyles.ts`\n\nEvery widget type has a default style object and an override factory:\n\n```typescript\n\u002F\u002F Use defaults:\nconst button = new Button(container, defaultButtonStyles);\n\n\u002F\u002F Override specific colors:\nconst button = new Button(container, getButtonStyles({\n    buttonBackground: myCustomBackgroundColor\n}));\n```\n\nAvailable defaults: `defaultButtonStyles`, `defaultInputBoxStyles`, `defaultCheckboxStyles`, `defaultToggleStyles`, `defaultDialogStyles`, `defaultListStyles`, `defaultSelectBoxStyles`, `defaultMenuStyles`, `defaultProgressBarStyles`, `defaultCountBadgeStyles`, `defaultBreadcrumbsWidgetStyles`, `defaultKeybindingLabelStyles`, `defaultFindWidgetStyles`.\n\n### Transient Theme Overrides\n\nUse the owning theme service for temporary palettes so CSS variables and programmatic color consumers remain consistent. Keep overrides scoped to the intended window and preserve the base theme and user customizations.\n\nVerify enabling, disabling, replacement, disposal, and theme changes, including stale asynchronous results. Clearing an override must restore the original colors without persisting generated values or changing another window's theme or startup colors.\n\n## 5. Focus Indicators\n\nDefined in `src\u002Fvs\u002Fworkbench\u002Fbrowser\u002Fmedia\u002Fstyle.css`:\n\n```css\n.my-widget:focus {\n    outline-width: 1px;\n    outline-style: solid;\n    outline-offset: -1px;\n    outline-color: var(--vscode-focusBorder);\n}\n```\n\n**Rules**:\n- Use `var(--vscode-focusBorder)` — never hardcode a focus color.\n- Default `outline-offset: -1px` (inset). Exception: checkboxes use `2px`.\n- Active elements suppress focus ring: `.my-widget:active { outline: 0 !important; }`\n- Use `.synthetic-focus` class for programmatic focus indication.\n- Toggle buttons use `border: 1px dashed var(--vscode-focusBorder)` instead of outline.\n- Check keyboard focus independently from selection and hover, including ordinary links without explicit `tabindex` and icon-only controls. Inspect computed outlines and pseudo-elements under production styles; token registration alone does not establish visibility.\n- Preserve a clear focus boundary through clipping and modal wrappers. Resolve competing border\u002Foutline ownership rather than adding duplicate rings or removing focus visibility.\n\n### Focus Trapping\n\nModal dialogs must trap focus within the dialog until dismissed. Use `dom.trackFocus()` and handle `Tab`\u002F`Shift+Tab` cycling.\n\n## 6. High Contrast Theme Rules\n\n- **Always** provide `hcDark` and `hcLight` defaults when registering colors.\n- HC backgrounds: `Color.black` (hcDark), `Color.white` (hcLight).\n- HC borders: reference `contrastBorder` — it is `null` in normal themes, visible in HC.\n- HC focus: use `activeContrastBorder` (derived from `focusBorder`).\n- In CSS, use `.hc-black` \u002F `.hc-light` class selectors for HC-specific overrides:\n  ```css\n  .hc-black .my-widget { border: 1px solid var(--vscode-contrastBorder); }\n  ```\n- In TypeScript, check `isHighContrast(theme.type)` for runtime behavior changes.\n- **Box shadows** must be removed or replaced in HC mode (shadows are invisible\u002Fdistracting with high contrast borders):\n  ```css\n  .my-widget {\n      box-shadow: 0 1px 3px var(--vscode-widget-shadow);\n  }\n  .vscode-high-contrast .my-widget {\n      box-shadow: none;\n      border: 1px solid var(--vscode-contrastBorder);\n  }\n  ```\n\nValidate both HC themes explicitly when changing borders, focus, or theme-dependent visibility; default dark\u002Flight screenshots do not cover them. Render through the production state-owning services so intentionally omitted decoration remains absent.\n\nTest runtime theme changes and custom color overrides, including transitions where a previously defined token becomes absent. Clear stale inline colors or classes rather than leaving the previous theme's state behind. Include competing workbench styles when inspecting the cascade.\n\n## 7. No Hardcoded Visual Values\n\nReviewers will always flag hardcoded colors, shadows, sizes that should use theme tokens or CSS variables.\n\n| Hardcoded (flagged) | Correct |\n|---------------------|---------|\n| `rgba(0, 0, 0, 0.12)` | `var(--vscode-widget-shadow)` or theme-aware variable |\n| `#252526` | `var(--vscode-editor-background)` |\n| `color: white` | `var(--vscode-button-foreground)` |\n| `border: 1px solid #ccc` | `var(--vscode-editorWidget-border)` |\n| `border: 1px solid …` (width) | `var(--vscode-strokeThickness)` for the 1px width |\n| `border-radius: 6px` | `var(--vscode-cornerRadius-medium)` (radius ramp) |\n| `padding: 8px 12px` (off-scale) | spacing ramp (`--vscode-spacing-size*`) |\n| `font-size: 14px` (arbitrary) | size ramp (`--vscode-fontSize-*`) |\n| `font-weight: 500` | `--vscode-fontWeight-semiBold` (no 500) |\n| codicon `font-size: 14px` | `--vscode-codiconFontSize` (16) \u002F `-compact` (12) |\n\n**Rule:** If a value relates to color, shadow, or border — it must come from a CSS variable or registered color token. The only exception is `0` (zero) values and purely structural measurements like `100%`.\n\n**Size, spacing, radius, font and stroke** values have their own design-system **size** tokens (and decision logic — snap maps, the pill→`circle` rule, and the compact-glyph convention). Those live in the **ux-css-layout** skill (§10 Design-System Size Tokens) and the auto-injected `.github\u002Finstructions\u002Fdesign-tokens.instructions.md`. Reach for those when a flag is about *how big \u002F how round \u002F how bold* something is rather than *what color*.\n\n---\n\n## Key Files\n\n| Area | File |\n|------|------|\n| Color registration | `src\u002Fvs\u002Fplatform\u002Ftheme\u002Fcommon\u002FcolorUtils.ts` |\n| Color registry (barrel) | `src\u002Fvs\u002Fplatform\u002Ftheme\u002Fcommon\u002FcolorRegistry.ts` |\n| Base colors | `src\u002Fvs\u002Fplatform\u002Ftheme\u002Fcommon\u002Fcolors\u002FbaseColors.ts` |\n| Workbench colors | `src\u002Fvs\u002Fworkbench\u002Fcommon\u002Ftheme.ts` |\n| Default widget styles | `src\u002Fvs\u002Fplatform\u002Ftheme\u002Fbrowser\u002FdefaultStyles.ts` |\n| Global workbench styles | `src\u002Fvs\u002Fworkbench\u002Fbrowser\u002Fmedia\u002Fstyle.css` |\n",{"name":5,"description":7},"main","4991a88ff5fb439088caf416d41d54d81446539d",".github\u002Fskills\u002Fux-theming",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":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add microsoft\u002Fvscode --skill ux-theming",{"tool":65,"command":66},"bunx","bunx skills add microsoft\u002Fvscode --skill ux-theming",{"tool":68,"command":69},"pnpm","pnpm dlx skills add microsoft\u002Fvscode --skill ux-theming","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fux-theming\u002FSKILL.md",true,[],[74,99,121,135,149,165],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":44},"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",[],[81,82,83,84,85,27,86,87,88,89,90,91,92,93,94,95,96,97,98,43],"sweeper query","query","sweeper","review","fix","request","which","natural-language","ranking","duplicates","ready","only","read","plan","open","Citations","brief","issues",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":44},"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",[],[106,107,108,109,110,111,112,40,113,114,115,116,117,118,119,120,27],"update","update skills","for","pattern","domain","learnings","reusable","session","user","instructions","knowledge","repository","learn","create","sessions",{"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":44},"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",[],[106,128,129,27,86,130,108,40,113,114,131,132,133,134],"pr","update pr","Existing","push","pull","pull request","changes",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":44},"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",[],[137,142,143,131,132,144,27,134,145,33,146,147,40,113,114,148],"SET","publish","rebase","latest","remote","upstream","branch",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":44},"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",[],[147,137,156,157,27,158,159,134,145,160,161,162,163,40,113,148,164,106],"sync upstream","fit","catch","catch up","origin","conflicts","stale","up","work",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":44},"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",[],[167,113,40,164,148,114,27,172,173,134],"back","base"]