[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699AY3ZWT6EFHKEWJT6TS25":3,"skill-same:01M699AY3ZWT6EFHKEWJT6TS25":69},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M699AY3ZWT6EFHKEWJT6TS25","integration-tests",null,"Use when running integration tests in the VS Code repo. Covers scripts\u002Ftest-integration.sh (macOS\u002FLinux) and scripts\u002Ftest-integration.bat (Windows), their supported arguments for filtering, and the difference between node.js integration tests and extension host tests.","microsoft\u002Fvscode","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M6998NK2WED5M549DX06VBCH",195369,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fintegration-tests\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"integration tests","integration","tests","filtering","running","when","for","scripts","extension","host","bat","Running Integration Tests","use","macos","repo","node","js","code","windows","test","linux","2026-11-10 10:12:30",false,"---\nname: integration-tests\ndescription: Use when running integration tests in the VS Code repo. Covers scripts\u002Ftest-integration.sh (macOS\u002FLinux) and scripts\u002Ftest-integration.bat (Windows), their supported arguments for filtering, and the difference between node.js integration tests and extension host tests.\n---\n\n# Running Integration Tests\n\nIntegration tests in VS Code are split into two categories:\n\n1. **Node.js integration tests** - files ending in `.integrationTest.ts` under `src\u002F`. These run in Electron via the same Mocha runner as unit tests.\n2. **Extension host tests** - tests embedded in built-in extensions under `extensions\u002F` (API tests, Git tests, TypeScript tests, etc.). These launch a full VS Code instance with `--extensionDevelopmentPath`.\n\n## Scripts\n\n- **macOS \u002F Linux:** `.\u002Fscripts\u002Ftest-integration.sh [options]`\n- **Windows:** `.\\scripts\\test-integration.bat [options]`\n\nWhen run **without filters**, both scripts execute all node.js integration tests followed by all extension host tests. They do **not** run the deterministic Agent Host E2E suites: those run with `.\u002Fscripts\u002Ftest-agent-host-e2e.sh` (or `.\\scripts\\test-agent-host-e2e.bat`, or `pnpm run test-agent-host-e2e`), which runs each suite in its own isolated test process, in parallel. GitHub CI runs them in parallel with the integration tests, in the separate `Linux \u002F Agent-Host-E2E` job on Linux and the `Windows \u002F Agent-Host-E2E (shard 1\u002F3)` through `Windows \u002F Agent-Host-E2E (shard 3\u002F3)` jobs on Windows, and as a separate step before `🧪 Run integration tests (Electron)` on macOS; ADO runs them as the `integration-agent-host-e2e` test ID in a separate `Agent Host E2E Tests (Electron)` job, not in the `Integration Tests (Electron)` job (`integration-electron`). See `src\u002Fvs\u002Fplatform\u002FagentHost\u002Ftest\u002Fnode\u002Fe2e\u002FREADME.md`. `--run` still accepts a single Agent Host E2E file.\n\nWhen run **with `--run` or `--runGlob`** (without `--suite`), only the node.js integration tests are run and the filter is applied. Extension host tests are skipped since these filters are node.js-specific.\n\nWhen run **with `--grep` alone** (no `--run`, `--runGlob`, or `--suite`), all tests are run -- both node.js integration tests and all extension host suites -- with the grep pattern forwarded to every test runner.\n\nWhen run **with `--suite`**, only the matching extension host test suites are run. Node.js integration tests are skipped. Combine `--suite` with `--grep` to filter individual tests within the selected suites.\n\n## Options\n\n### `--build` - Run against build output\n\nSelects the `out-build\u002F` directory instead of `out\u002F` for node.js integration tests and the shared VS Code modules used by the standalone JSON suite. This does not compile either output tree; the JSON extension tests still require `compile-extension:json-language-features-client` to generate `client\u002Fout\u002F`.\n\n```bash\n.\u002Fscripts\u002Ftest-integration.sh --suite json --build\n```\n\n### `--run \u003Cfile>` - Run tests from a specific file\n\nAccepts a **source file path** (starting with `src\u002F`). Works identically to `scripts\u002Ftest.sh --run`.\n\n```bash\n.\u002Fscripts\u002Ftest-integration.sh --run src\u002Fvs\u002Fworkbench\u002Fservices\u002Fsearch\u002Ftest\u002Fnode\u002Fsearch.integrationTest.ts\n```\n\n### `--runGlob \u003Cpattern>` (aliases: `--glob`, `--runGrep`) - Select test files by path\n\nSelects which test **files** to load by matching compiled `.js` file paths against a glob pattern. Overrides the default `**\u002F*.integrationTest.js` glob. Only applies to node.js integration tests (extension host tests are skipped).\n\n```bash\n.\u002Fscripts\u002Ftest-integration.sh --runGlob \"**\u002Fsearch\u002F**\u002F*.integrationTest.js\"\n```\n\n### `--grep \u003Cpattern>` (aliases: `-g`, `-f`) - Filter test cases by name\n\nFilters which **test cases** run by matching against their test titles (e.g. `describe`\u002F`test` names). When used alone, the grep is applied to both node.js integration tests and all extension host suites. When combined with `--suite`, only the matched suites run with the grep.\n\n```bash\n.\u002Fscripts\u002Ftest-integration.sh --grep \"TextSearchProvider\"\n```\n\n### `--suite \u003Cpattern>` - Run specific extension host test suites\n\nRuns only the extension host test suites whose name matches the pattern. Supports comma-separated values and shell glob patterns (on macOS\u002FLinux). Node.js integration tests are skipped.\n\nAvailable suite names: `api-folder`, `api-workspace`, `colorize`, `terminal-suggest`, `typescript`, `markdown`, `emmet`, `git`, `git-base`, `ipynb`, `notebook-renderers`, `configuration-editing`, `github-authentication`, `copilot`, `css`, `html`, `json`.\n\nThe `css`, `html`, and `json` suites are standalone extension tests that run in Electron's Node.js mode without opening a workbench. They share the same suite selection and grep filtering as extension host tests.\n\n```bash\n# Run only Git extension tests\n.\u002Fscripts\u002Ftest-integration.sh --suite git\n\n# Run API folder and workspace tests (glob, macOS\u002FLinux only)\n.\u002Fscripts\u002Ftest-integration.sh --suite 'api*'\n\n# Run multiple specific suites\n.\u002Fscripts\u002Ftest-integration.sh --suite 'git,emmet,typescript'\n\n# Filter tests within a suite by name\n.\u002Fscripts\u002Ftest-integration.sh --suite api-folder --grep 'should open'\n```\n\n### `--only-node-tests`, `--only-extension-host-tests` - Run one part\n\nRuns only the node.js integration tests, or only the extension host tests (all suites, including `css`, `html` and `json`). `--grep` still applies to both. `--only-node-tests` cannot be combined with `--suite`, and `--only-extension-host-tests` cannot be combined with `--run` or `--runGlob`.\n\nGitHub pull request CI runs the two parts as separate steps. `🧪 Run integration tests (Electron)` runs the node.js integration tests and reruns failed tests (`--rerun-failed-files 2`). `🧪 Run extension host integration tests (Electron)` runs the extension host suites, which are not rerun; it also runs after the integration tests or Agent Host E2E failed. The Azure Pipelines product build runs both parts in one step with `--rerun-failed-files 2`, which only reruns the failed node.js integration tests.\n\n```bash\n.\u002Fscripts\u002Ftest-integration.sh --only-node-tests --rerun-failed-files 2\n.\u002Fscripts\u002Ftest-integration.sh --only-extension-host-tests\n```\n\n### `INTEGRATION_TEST_PARALLEL=\u003Clanes>` - Run extension host suites in parallel\n\nMost of an extension host suite is starting VS Code, so with this environment variable, `scripts\u002Ftest-integration.sh` and `scripts\u002Ftest-remote-integration.sh` (macOS\u002FLinux) run up to `\u003Clanes>` suites at the same time, the longest first, each with its own user data and logs folders. Unless `VSCODE_SKIP_PRELAUNCH` is set, Electron, the compiled sources and the built-in extensions are prepared once before the suites start, instead of at each launch. Each suite's output is printed when it finishes, and the run fails at the end when any suite failed. Without it, the suites run one after another and the first failure stops the run. The Linux and macOS PR jobs set it to 2 (see `scripts\u002Fintegration-test-suites.sh`). The API tests wait a fixed time for tools to register and for browser pages to respond, and another instance competing for the CPU delays them past that time, so they run first, with no other suite at the same time (`run_group_alone api`).\n\n```bash\nINTEGRATION_TEST_PARALLEL=2 .\u002Fscripts\u002Ftest-integration.sh --only-extension-host-tests\n```\n\n### `--help`, `-h` - Show help\n\n```bash\n.\u002Fscripts\u002Ftest-integration.sh --help\n```\n\n### Other options\n\nAll other options (e.g. `--timeout`, `--coverage`, `--reporter`) are forwarded to the underlying `scripts\u002Ftest.sh` runner for node.js integration tests. These extra options are **not** forwarded to extension host suites when using `--suite`.\n\n## Examples\n\n```bash\n# Run all integration tests (node.js + extension host)\n.\u002Fscripts\u002Ftest-integration.sh\n\n# Run a single integration test file\n.\u002Fscripts\u002Ftest-integration.sh --run src\u002Fvs\u002Fworkbench\u002Fservices\u002Fsearch\u002Ftest\u002Fnode\u002Fsearch.integrationTest.ts\n\n# Run integration tests matching a grep pattern\n.\u002Fscripts\u002Ftest-integration.sh --grep \"TextSearchProvider\"\n\n# Run integration tests under a specific area\n.\u002Fscripts\u002Ftest-integration.sh --runGlob \"**\u002Fworkbench\u002F**\u002F*.integrationTest.js\"\n\n# Run only Git extension host tests\n.\u002Fscripts\u002Ftest-integration.sh --suite git\n\n# Run API folder + workspace extension tests (glob)\n.\u002Fscripts\u002Ftest-integration.sh --suite 'api*'\n\n# Run multiple extension test suites\n.\u002Fscripts\u002Ftest-integration.sh --suite 'git,typescript,emmet'\n\n# Grep for specific tests in the API folder suite\n.\u002Fscripts\u002Ftest-integration.sh --suite api-folder --grep 'should open'\n\n# Combine file and grep\n.\u002Fscripts\u002Ftest-integration.sh --run src\u002Fvs\u002Fworkbench\u002Fservices\u002Fsearch\u002Ftest\u002Fnode\u002Fsearch.integrationTest.ts --grep \"should search\"\n```\n\n## Compilation requirement\n\nTests run against compiled JavaScript output. Ensure the `VS Code - Build` watch task is running or that compilation has completed before running tests.\n\n## Distinction from unit tests\n\n- **Unit tests** (`.test.ts`) → use `scripts\u002Ftest.sh` or the `runTests` tool\n- **Integration tests** (`.integrationTest.ts` and extension tests) → use `scripts\u002Ftest-integration.sh`\n\nDo **not** mix these up: `scripts\u002Ftest.sh` will not find integration test files unless you explicitly pass `--runGlob **\u002F*.integrationTest.js`, and `scripts\u002Ftest-integration.sh` is not intended for `.test.ts` files.\n","# Running Integration Tests\n\nIntegration tests in VS Code are split into two categories:\n\n1. **Node.js integration tests** - files ending in `.integrationTest.ts` under `src\u002F`. These run in Electron via the same Mocha runner as unit tests.\n2. **Extension host tests** - tests embedded in built-in extensions under `extensions\u002F` (API tests, Git tests, TypeScript tests, etc.). These launch a full VS Code instance with `--extensionDevelopmentPath`.\n\n## Scripts\n\n- **macOS \u002F Linux:** `.\u002Fscripts\u002Ftest-integration.sh [options]`\n- **Windows:** `.\\scripts\\test-integration.bat [options]`\n\nWhen run **without filters**, both scripts execute all node.js integration tests followed by all extension host tests. They do **not** run the deterministic Agent Host E2E suites: those run with `.\u002Fscripts\u002Ftest-agent-host-e2e.sh` (or `.\\scripts\\test-agent-host-e2e.bat`, or `pnpm run test-agent-host-e2e`), which runs each suite in its own isolated test process, in parallel. GitHub CI runs them in parallel with the integration tests, in the separate `Linux \u002F Agent-Host-E2E` job on Linux and the `Windows \u002F Agent-Host-E2E (shard 1\u002F3)` through `Windows \u002F Agent-Host-E2E (shard 3\u002F3)` jobs on Windows, and as a separate step before `🧪 Run integration tests (Electron)` on macOS; ADO runs them as the `integration-agent-host-e2e` test ID in a separate `Agent Host E2E Tests (Electron)` job, not in the `Integration Tests (Electron)` job (`integration-electron`). See `src\u002Fvs\u002Fplatform\u002FagentHost\u002Ftest\u002Fnode\u002Fe2e\u002FREADME.md`. `--run` still accepts a single Agent Host E2E file.\n\nWhen run **with `--run` or `--runGlob`** (without `--suite`), only the node.js integration tests are run and the filter is applied. Extension host tests are skipped since these filters are node.js-specific.\n\nWhen run **with `--grep` alone** (no `--run`, `--runGlob`, or `--suite`), all tests are run -- both node.js integration tests and all extension host suites -- with the grep pattern forwarded to every test runner.\n\nWhen run **with `--suite`**, only the matching extension host test suites are run. Node.js integration tests are skipped. Combine `--suite` with `--grep` to filter individual tests within the selected suites.\n\n## Options\n\n### `--build` - Run against build output\n\nSelects the `out-build\u002F` directory instead of `out\u002F` for node.js integration tests and the shared VS Code modules used by the standalone JSON suite. This does not compile either output tree; the JSON extension tests still require `compile-extension:json-language-features-client` to generate `client\u002Fout\u002F`.\n\n```bash\n.\u002Fscripts\u002Ftest-integration.sh --suite json --build\n```\n\n### `--run \u003Cfile>` - Run tests from a specific file\n\nAccepts a **source file path** (starting with `src\u002F`). Works identically to `scripts\u002Ftest.sh --run`.\n\n```bash\n.\u002Fscripts\u002Ftest-integration.sh --run src\u002Fvs\u002Fworkbench\u002Fservices\u002Fsearch\u002Ftest\u002Fnode\u002Fsearch.integrationTest.ts\n```\n\n### `--runGlob \u003Cpattern>` (aliases: `--glob`, `--runGrep`) - Select test files by path\n\nSelects which test **files** to load by matching compiled `.js` file paths against a glob pattern. Overrides the default `**\u002F*.integrationTest.js` glob. Only applies to node.js integration tests (extension host tests are skipped).\n\n```bash\n.\u002Fscripts\u002Ftest-integration.sh --runGlob \"**\u002Fsearch\u002F**\u002F*.integrationTest.js\"\n```\n\n### `--grep \u003Cpattern>` (aliases: `-g`, `-f`) - Filter test cases by name\n\nFilters which **test cases** run by matching against their test titles (e.g. `describe`\u002F`test` names). When used alone, the grep is applied to both node.js integration tests and all extension host suites. When combined with `--suite`, only the matched suites run with the grep.\n\n```bash\n.\u002Fscripts\u002Ftest-integration.sh --grep \"TextSearchProvider\"\n```\n\n### `--suite \u003Cpattern>` - Run specific extension host test suites\n\nRuns only the extension host test suites whose name matches the pattern. Supports comma-separated values and shell glob patterns (on macOS\u002FLinux). Node.js integration tests are skipped.\n\nAvailable suite names: `api-folder`, `api-workspace`, `colorize`, `terminal-suggest`, `typescript`, `markdown`, `emmet`, `git`, `git-base`, `ipynb`, `notebook-renderers`, `configuration-editing`, `github-authentication`, `copilot`, `css`, `html`, `json`.\n\nThe `css`, `html`, and `json` suites are standalone extension tests that run in Electron's Node.js mode without opening a workbench. They share the same suite selection and grep filtering as extension host tests.\n\n```bash\n# Run only Git extension tests\n.\u002Fscripts\u002Ftest-integration.sh --suite git\n\n# Run API folder and workspace tests (glob, macOS\u002FLinux only)\n.\u002Fscripts\u002Ftest-integration.sh --suite 'api*'\n\n# Run multiple specific suites\n.\u002Fscripts\u002Ftest-integration.sh --suite 'git,emmet,typescript'\n\n# Filter tests within a suite by name\n.\u002Fscripts\u002Ftest-integration.sh --suite api-folder --grep 'should open'\n```\n\n### `--only-node-tests`, `--only-extension-host-tests` - Run one part\n\nRuns only the node.js integration tests, or only the extension host tests (all suites, including `css`, `html` and `json`). `--grep` still applies to both. `--only-node-tests` cannot be combined with `--suite`, and `--only-extension-host-tests` cannot be combined with `--run` or `--runGlob`.\n\nGitHub pull request CI runs the two parts as separate steps. `🧪 Run integration tests (Electron)` runs the node.js integration tests and reruns failed tests (`--rerun-failed-files 2`). `🧪 Run extension host integration tests (Electron)` runs the extension host suites, which are not rerun; it also runs after the integration tests or Agent Host E2E failed. The Azure Pipelines product build runs both parts in one step with `--rerun-failed-files 2`, which only reruns the failed node.js integration tests.\n\n```bash\n.\u002Fscripts\u002Ftest-integration.sh --only-node-tests --rerun-failed-files 2\n.\u002Fscripts\u002Ftest-integration.sh --only-extension-host-tests\n```\n\n### `INTEGRATION_TEST_PARALLEL=\u003Clanes>` - Run extension host suites in parallel\n\nMost of an extension host suite is starting VS Code, so with this environment variable, `scripts\u002Ftest-integration.sh` and `scripts\u002Ftest-remote-integration.sh` (macOS\u002FLinux) run up to `\u003Clanes>` suites at the same time, the longest first, each with its own user data and logs folders. Unless `VSCODE_SKIP_PRELAUNCH` is set, Electron, the compiled sources and the built-in extensions are prepared once before the suites start, instead of at each launch. Each suite's output is printed when it finishes, and the run fails at the end when any suite failed. Without it, the suites run one after another and the first failure stops the run. The Linux and macOS PR jobs set it to 2 (see `scripts\u002Fintegration-test-suites.sh`). The API tests wait a fixed time for tools to register and for browser pages to respond, and another instance competing for the CPU delays them past that time, so they run first, with no other suite at the same time (`run_group_alone api`).\n\n```bash\nINTEGRATION_TEST_PARALLEL=2 .\u002Fscripts\u002Ftest-integration.sh --only-extension-host-tests\n```\n\n### `--help`, `-h` - Show help\n\n```bash\n.\u002Fscripts\u002Ftest-integration.sh --help\n```\n\n### Other options\n\nAll other options (e.g. `--timeout`, `--coverage`, `--reporter`) are forwarded to the underlying `scripts\u002Ftest.sh` runner for node.js integration tests. These extra options are **not** forwarded to extension host suites when using `--suite`.\n\n## Examples\n\n```bash\n# Run all integration tests (node.js + extension host)\n.\u002Fscripts\u002Ftest-integration.sh\n\n# Run a single integration test file\n.\u002Fscripts\u002Ftest-integration.sh --run src\u002Fvs\u002Fworkbench\u002Fservices\u002Fsearch\u002Ftest\u002Fnode\u002Fsearch.integrationTest.ts\n\n# Run integration tests matching a grep pattern\n.\u002Fscripts\u002Ftest-integration.sh --grep \"TextSearchProvider\"\n\n# Run integration tests under a specific area\n.\u002Fscripts\u002Ftest-integration.sh --runGlob \"**\u002Fworkbench\u002F**\u002F*.integrationTest.js\"\n\n# Run only Git extension host tests\n.\u002Fscripts\u002Ftest-integration.sh --suite git\n\n# Run API folder + workspace extension tests (glob)\n.\u002Fscripts\u002Ftest-integration.sh --suite 'api*'\n\n# Run multiple extension test suites\n.\u002Fscripts\u002Ftest-integration.sh --suite 'git,typescript,emmet'\n\n# Grep for specific tests in the API folder suite\n.\u002Fscripts\u002Ftest-integration.sh --suite api-folder --grep 'should open'\n\n# Combine file and grep\n.\u002Fscripts\u002Ftest-integration.sh --run src\u002Fvs\u002Fworkbench\u002Fservices\u002Fsearch\u002Ftest\u002Fnode\u002Fsearch.integrationTest.ts --grep \"should search\"\n```\n\n## Compilation requirement\n\nTests run against compiled JavaScript output. Ensure the `VS Code - Build` watch task is running or that compilation has completed before running tests.\n\n## Distinction from unit tests\n\n- **Unit tests** (`.test.ts`) → use `scripts\u002Ftest.sh` or the `runTests` tool\n- **Integration tests** (`.integrationTest.ts` and extension tests) → use `scripts\u002Ftest-integration.sh`\n\nDo **not** mix these up: `scripts\u002Ftest.sh` will not find integration test files unless you explicitly pass `--runGlob **\u002F*.integrationTest.js`, and `scripts\u002Ftest-integration.sh` is not intended for `.test.ts` files.\n",{"name":5,"description":7},"main","4991a88ff5fb439088caf416d41d54d81446539d",".github\u002Fskills\u002Fintegration-tests",43835,"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-15 03:00:24",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add microsoft\u002Fvscode --skill integration-tests",{"tool":61,"command":62},"bunx","bunx skills add microsoft\u002Fvscode --skill integration-tests",{"tool":64,"command":65},"pnpm","pnpm dlx skills add microsoft\u002Fvscode --skill integration-tests","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fintegration-tests\u002FSKILL.md",true,[],[70,95,116,130,145,161],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":40},"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",[],[77,78,79,80,81,24,82,83,84,85,86,87,88,89,90,91,92,93,94,36],"sweeper query","query","sweeper","review","fix","request","which","natural-language","ranking","duplicates","ready","only","read","plan","open","Citations","brief","issues",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":40},"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",[],[102,103,25,104,105,106,107,31,108,109,110,111,112,113,114,115,24],"update","update skills","pattern","domain","learnings","reusable","session","user","instructions","knowledge","repository","learn","create","sessions",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":40},"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",[],[102,123,124,24,82,125,25,31,108,109,126,127,128,129],"pr","update pr","Existing","push","pull","pull request","changes",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":40},"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",[],[132,137,138,126,127,139,24,129,140,141,142,143,31,108,109,144],"SET","publish","rebase","latest","with","remote","upstream","branch",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":40},"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",[],[143,132,152,153,24,154,155,129,140,156,157,158,159,31,108,144,160,102],"sync upstream","fit","catch","catch up","origin","conflicts","stale","up","work",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":40},"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",[],[163,108,31,160,144,109,24,168,169,129],"back","base"]