[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69B6CQT3K9X5HSCQ10ZX54T":3,"skill-same:01M69B6CQT3K9X5HSCQ10ZX54T":75},{"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},"01M69B6CQT3K9X5HSCQ10ZX54T","pr-readiness",null,"Verify that a pull request into microsoft\u002Fvscode-cmake-tools meets contribution requirements. Use when preparing, reviewing, or finalizing a PR to check for a descriptive title, a meaningful description, a properly formatted CHANGELOG entry, code correctness, regression risks, adherence to existing patterns, and whether documentation updates are needed.","microsoft\u002Fvscode-cmake-tools","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69B5ZETEJ3WM91BA2ZYMTYT",1688,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-cmake-tools\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpr-readiness\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,9,32,33,34,35,36,37,38,39],"pr","pr readiness","readiness","check","when","title","Existing","for","updates","correctness","contribution","requirements","use","regression","pull","changelog","code","cmake","pull request","documentation","vscode","2026-11-10 10:12:30",false,"---\nname: pr-readiness\ndescription: >\n  Verify that a pull request into microsoft\u002Fvscode-cmake-tools meets contribution\n  requirements. Use when preparing, reviewing, or finalizing a PR to check for a\n  descriptive title, a meaningful description, a properly formatted CHANGELOG entry,\n  code correctness, regression risks, adherence to existing patterns, and whether\n  documentation updates are needed.\n---\n\n# PR Readiness\n\n## PR Requirements Checklist\n\n### 1. PR Title\n\nThe title must clearly and concisely describe the change from the user's perspective. It should:\n\n- Start with a verb (e.g., \"Fix\", \"Add\", \"Improve\", \"Remove\", \"Update\").\n- Mention the affected feature or area (e.g., presets, kits, CTest, build tasks, Project Outline).\n- Be specific enough that a reader understands the change without opening the PR.\n\n**Good examples:**\n\n- `Fix preset reloading loop when preset files are symlinks`\n- `Add \"Delete Build Directory and Reconfigure\" command`\n- `Improve CTest test ordering to match Test Explorer display`\n\n**Bad examples:**\n\n- `Fix bug` (too vague)\n- `Update code` (no useful information)\n- `WIP` (not ready for review)\n\n### 2. PR Description\n\nThe PR body must include:\n\n- **What changed**: A short summary of the user-visible behavior change.\n- **Why**: The motivation — link to a GitHub issue if one exists (e.g., `Fixes #1234`).\n- **How** (if non-obvious): A brief explanation of the implementation approach when the change is complex.\n\n### 3. CHANGELOG Entry\n\nEvery PR must add an entry to `CHANGELOG.md`.\n\n#### Where to insert\n\nInsert the entry under the **most recent (topmost) version heading** in `CHANGELOG.md`. The first version heading looks like `## \u003Cversion>` (e.g., `## 1.23`). Always add the new entry at the **bottom** of the appropriate section (i.e., after all existing entries in that section).\n\n#### Which section\n\nPlace the entry in exactly one of these three sections, creating the section if it does not already exist under the current version:\n\n| Section | Use when… |\n|---|---|\n| `Features:` | A new user-visible capability is added (new command, new setting, new UI element). |\n| `Improvements:` | An existing feature is enhanced, optimized, or has better UX — but no new capability is introduced. |\n| `Bug Fixes:` | A defect is corrected. |\n\nThe sections appear in this fixed order: `Features:`, then `Improvements:`, then `Bug Fixes:`.\n\n#### Entry format\n\nEach entry follows this pattern:\n\n```\n- \u003CDescription>. [#\u003Cnumber>](\u003Clink>)\n```\n\nWhere `\u003CDescription>` starts with a present-tense verb describing the user-visible change, and the link references either:\n\n- The **GitHub issue** it solves: `[#\u003Cissue number>](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-cmake-tools\u002Fissues\u002F\u003Cissue number>)`\n- Or the **PR** itself: `[#\u003Cpr number>](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-cmake-tools\u002Fpull\u002F\u003Cpr number>)`\n\nAn entry may optionally credit an external contributor at the end: `[@user](https:\u002F\u002Fgithub.com\u002Fuser)`.\n\n**Examples:**\n\n```markdown\nFeatures:\n- Add \"Delete Build Directory and Reconfigure\" command that removes the entire build directory before reconfiguring, ensuring a completely clean state. [#4826](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-cmake-tools\u002Fpull\u002F4826)\n\nImprovements:\n- Run tests sequentially in alphabetical order (matching the Test Explorer display order) when `cmake.ctest.allowParallelJobs` is disabled. [#4829](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-cmake-tools\u002Fissues\u002F4829)\n\nBug Fixes:\n- Fix `cmake.revealLog` set to `\"focus\"` not revealing the output panel or stealing focus. [#4471](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-cmake-tools\u002Fissues\u002F4471)\n- Fix garbled characters in the Output panel when MSVC outputs UTF-8 on non-UTF-8 Windows systems. [#4520](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-cmake-tools\u002Fissues\u002F4520) [@contributor](https:\u002F\u002Fgithub.com\u002Fcontributor)\n```\n\n#### What NOT to do\n\n- Do **not** add a new version heading — use the existing topmost one.\n- Do **not** place the entry under an older version.\n- Do **not** use past tense (write \"Fix …\", not \"Fixed …\").\n- Do **not** omit the issue or PR link.\n\n### 4. Correctness\n\nReview the code changes for logical correctness:\n\n- **Both operating modes**: If the change touches shared logic (configure, build, test, targets, environment), verify it handles both *presets mode* and *kits\u002Fvariants mode*. Check for `useCMakePresets` branching where appropriate.\n- **Both generator types**: If the change involves build-type logic, verify it handles both single-config generators (`CMAKE_BUILD_TYPE` at configure time) and multi-config generators (`--config` at build time).\n- **Edge cases**: Look for off-by-one errors, null\u002Fundefined access, missing `await` on async calls, and unhandled promise rejections.\n- **Error handling**: Verify errors are not silently swallowed. Top-level event handlers should use `rollbar.invokeAsync()` \u002F `rollbar.invoke()`. Empty `catch` blocks are a red flag.\n- **Cross-platform**: Check for hardcoded path separators (`\u002F` or `\\\\`), case-sensitive env var assumptions, or platform-specific APIs used without guards. Paths must use `path.join()` \u002F `path.normalize()`.\n\n### 5. Regression Risks\n\nIdentify areas where the change could break existing behavior:\n\n- **Shared utilities**: Changes to `src\u002Fexpand.ts`, `src\u002Fproc.ts`, `src\u002Fshlex.ts`, or `src\u002Futil.ts` affect many callers — verify all call sites still behave correctly.\n- **Driver base class**: Changes to `cmakeDriver.ts` propagate to `cmakeFileApiDriver.ts`, `cmakeLegacyDriver.ts`, and `cmakeServerDriver.ts`. Check that subclass overrides are still compatible.\n- **Preset merging**: Changes to `presetsController.ts` or `presetsParser.ts` can alter how presets resolve — verify with nested `include` chains and `CMakeUserPresets.json` overrides.\n- **Settings**: Adding or renaming a setting in `package.json` without updating `src\u002Fconfig.ts` (or vice versa) causes silent failures.\n- **Task provider**: Changes to `cmakeTaskProvider.ts` can break `tasks.json` definitions that users have already configured.\n- **Public API \u002F extensibility**: Changes to exports in `src\u002Fapi.ts` or types in `EXTENSIBILITY.md` can break dependent extensions.\n- **Test coverage**: Flag changes to critical paths that lack corresponding test updates, especially in `src\u002Fdrivers\u002F`, `src\u002Fpresets\u002F`, and `src\u002Fkits\u002F`. See also section 7 (Test Coverage) for detailed test review guidance.\n\n### 6. Adherence to Existing Patterns\n\nVerify the change follows the project's established conventions:\n\n- **Import style**: Uses `@cmt\u002F*` path aliases (not relative paths from outside `src\u002F`). Uses `import * as nls from 'vscode-nls'` for localization.\n- **Logging**: Uses `logging.createLogger('module-name')` — never `console.log`.\n- **Localization**: All user-visible strings use `localize('message.key', 'Message text')` with the `vscode-nls` boilerplate at the top of the file.\n- **Settings access**: Reads settings through `ConfigurationReader` (`src\u002Fconfig.ts`) — never calls `vscode.workspace.getConfiguration()` directly.\n- **Telemetry**: Uses helpers from `src\u002Ftelemetry.ts` — never calls the VS Code telemetry API directly.\n- **Data access**: Uses canonical data paths (e.g., `CMakeProject.targets` for targets, `CMakeDriver.cmakeCacheEntries` for cache) — never parses CMake files or cache directly.\n- **Async patterns**: Prefers `async`\u002F`await` over `.then()` chains (exception: fire-and-forget UI calls).\n- **Naming and structure**: New files are placed in the correct layer directory (see architecture table in `.github\u002Fcopilot-instructions.md`). New commands are registered in `src\u002Fextension.ts`.\n\n### 7. Test Coverage\n\nVerify that the PR includes adequate tests for the changes:\n\n- **New functionality**: Any new function, command, setting, or behavior branch should have corresponding tests. If the change adds a new helper or utility, check that it has unit tests covering its inputs and edge cases.\n- **Bug fixes**: A bug fix should include at least one test that would have caught the original bug — i.e., a test that fails on the base branch and passes with the fix applied.\n- **Changed behavior**: If existing behavior is modified, check that existing tests are updated to reflect the new behavior and that no tests are silently broken or deleted without justification.\n- **Test location**: Unit tests that don't require VS Code APIs belong in `test\u002Funit-tests\u002Fbackend\u002F` and run via `yarn backendTests`. Tests that require VS Code belong in `test\u002Funit-tests\u002F` and run via `yarn unitTests`. Check that new tests are placed in the correct location.\n- **Test quality**: Tests should be specific and descriptive:\n  - Test names should clearly state what is being tested and the expected outcome.\n  - Tests should assert specific values, not just \"no error thrown\".\n  - Tests should cover both positive cases (expected input → expected output) and negative\u002Fedge cases (invalid input, boundary conditions, fallback paths).\n  - Comments in tests should be accurate and not misleading about what the test actually exercises.\n- **Coverage gaps to flag**: Pay special attention to:\n  - Code paths that touch `src\u002Fdrivers\u002F`, `src\u002Fpresets\u002F`, or `src\u002Fkits\u002F` — these are critical and should have test coverage for any non-trivial changes.\n  - Fallback\u002Ferror paths — if the PR adds a fallback (e.g., \"if X fails, try Y\"), both the success and fallback paths should be tested.\n  - Platform-specific branches — if the code branches on `process.platform`, each branch should ideally be covered.\n- **When tests are not feasible**: Some changes (e.g., pure UI wiring, VS Code API integration) are difficult to unit test. In these cases, verify that the manual-checklist or PR description explains how to manually verify the change, and flag the gap rather than ignoring it.\n\n### 8. Documentation Updates\n\nCheck whether the change requires documentation updates:\n\n- **New or changed settings**: Must be reflected in all three locations — `package.json` (`contributes.configuration`), `src\u002Fconfig.ts` (`ConfigurationReader`), and `docs\u002Fcmake-settings.md`.\n- **New commands**: Must be documented in `package.json` (`contributes.commands`) and referenced in the relevant docs page under `docs\u002F`.\n- **User-visible behavior changes**: If the change alters how a feature works (not just fixes a bug), check whether `docs\u002F` pages describing that feature need updating.\n- **Extensibility changes**: If `src\u002Fapi.ts` or public types change, update `EXTENSIBILITY.md`.\n- **README**: If a new major feature is added, check whether `README.md` should mention it.\n\n## Applying This Skill\n\nWhen reviewing or preparing a PR:\n\n1. **Check the title** — rewrite it if it is vague or missing context.\n2. **Check the description** — ensure it explains what, why, and (if needed) how.\n3. **Check `CHANGELOG.md`** — verify an entry exists under the current version in the correct section with the correct format. If missing, add one.\n4. **Check correctness** — review code for logical errors, missing mode\u002Fgenerator handling, cross-platform issues, and error handling gaps.\n5. **Check regression risks** — identify areas where the change could break existing behavior and flag missing test coverage for critical paths.\n6. **Check pattern adherence** — verify the change follows established import, logging, localization, settings access, and architectural conventions.\n7. **Check test coverage** — verify that new or changed behavior has corresponding tests, bug fixes include regression tests, and tests are placed in the correct location with good quality.\n8. **Check documentation** — verify that new or changed settings, commands, and behavior are reflected in the appropriate docs.\n","# PR Readiness\n\n## PR Requirements Checklist\n\n### 1. PR Title\n\nThe title must clearly and concisely describe the change from the user's perspective. It should:\n\n- Start with a verb (e.g., \"Fix\", \"Add\", \"Improve\", \"Remove\", \"Update\").\n- Mention the affected feature or area (e.g., presets, kits, CTest, build tasks, Project Outline).\n- Be specific enough that a reader understands the change without opening the PR.\n\n**Good examples:**\n\n- `Fix preset reloading loop when preset files are symlinks`\n- `Add \"Delete Build Directory and Reconfigure\" command`\n- `Improve CTest test ordering to match Test Explorer display`\n\n**Bad examples:**\n\n- `Fix bug` (too vague)\n- `Update code` (no useful information)\n- `WIP` (not ready for review)\n\n### 2. PR Description\n\nThe PR body must include:\n\n- **What changed**: A short summary of the user-visible behavior change.\n- **Why**: The motivation — link to a GitHub issue if one exists (e.g., `Fixes #1234`).\n- **How** (if non-obvious): A brief explanation of the implementation approach when the change is complex.\n\n### 3. CHANGELOG Entry\n\nEvery PR must add an entry to `CHANGELOG.md`.\n\n#### Where to insert\n\nInsert the entry under the **most recent (topmost) version heading** in `CHANGELOG.md`. The first version heading looks like `## \u003Cversion>` (e.g., `## 1.23`). Always add the new entry at the **bottom** of the appropriate section (i.e., after all existing entries in that section).\n\n#### Which section\n\nPlace the entry in exactly one of these three sections, creating the section if it does not already exist under the current version:\n\n| Section | Use when… |\n|---|---|\n| `Features:` | A new user-visible capability is added (new command, new setting, new UI element). |\n| `Improvements:` | An existing feature is enhanced, optimized, or has better UX — but no new capability is introduced. |\n| `Bug Fixes:` | A defect is corrected. |\n\nThe sections appear in this fixed order: `Features:`, then `Improvements:`, then `Bug Fixes:`.\n\n#### Entry format\n\nEach entry follows this pattern:\n\n```\n- \u003CDescription>. [#\u003Cnumber>](\u003Clink>)\n```\n\nWhere `\u003CDescription>` starts with a present-tense verb describing the user-visible change, and the link references either:\n\n- The **GitHub issue** it solves: `[#\u003Cissue number>](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-cmake-tools\u002Fissues\u002F\u003Cissue number>)`\n- Or the **PR** itself: `[#\u003Cpr number>](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-cmake-tools\u002Fpull\u002F\u003Cpr number>)`\n\nAn entry may optionally credit an external contributor at the end: `[@user](https:\u002F\u002Fgithub.com\u002Fuser)`.\n\n**Examples:**\n\n```markdown\nFeatures:\n- Add \"Delete Build Directory and Reconfigure\" command that removes the entire build directory before reconfiguring, ensuring a completely clean state. [#4826](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-cmake-tools\u002Fpull\u002F4826)\n\nImprovements:\n- Run tests sequentially in alphabetical order (matching the Test Explorer display order) when `cmake.ctest.allowParallelJobs` is disabled. [#4829](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-cmake-tools\u002Fissues\u002F4829)\n\nBug Fixes:\n- Fix `cmake.revealLog` set to `\"focus\"` not revealing the output panel or stealing focus. [#4471](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-cmake-tools\u002Fissues\u002F4471)\n- Fix garbled characters in the Output panel when MSVC outputs UTF-8 on non-UTF-8 Windows systems. [#4520](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-cmake-tools\u002Fissues\u002F4520) [@contributor](https:\u002F\u002Fgithub.com\u002Fcontributor)\n```\n\n#### What NOT to do\n\n- Do **not** add a new version heading — use the existing topmost one.\n- Do **not** place the entry under an older version.\n- Do **not** use past tense (write \"Fix …\", not \"Fixed …\").\n- Do **not** omit the issue or PR link.\n\n### 4. Correctness\n\nReview the code changes for logical correctness:\n\n- **Both operating modes**: If the change touches shared logic (configure, build, test, targets, environment), verify it handles both *presets mode* and *kits\u002Fvariants mode*. Check for `useCMakePresets` branching where appropriate.\n- **Both generator types**: If the change involves build-type logic, verify it handles both single-config generators (`CMAKE_BUILD_TYPE` at configure time) and multi-config generators (`--config` at build time).\n- **Edge cases**: Look for off-by-one errors, null\u002Fundefined access, missing `await` on async calls, and unhandled promise rejections.\n- **Error handling**: Verify errors are not silently swallowed. Top-level event handlers should use `rollbar.invokeAsync()` \u002F `rollbar.invoke()`. Empty `catch` blocks are a red flag.\n- **Cross-platform**: Check for hardcoded path separators (`\u002F` or `\\\\`), case-sensitive env var assumptions, or platform-specific APIs used without guards. Paths must use `path.join()` \u002F `path.normalize()`.\n\n### 5. Regression Risks\n\nIdentify areas where the change could break existing behavior:\n\n- **Shared utilities**: Changes to `src\u002Fexpand.ts`, `src\u002Fproc.ts`, `src\u002Fshlex.ts`, or `src\u002Futil.ts` affect many callers — verify all call sites still behave correctly.\n- **Driver base class**: Changes to `cmakeDriver.ts` propagate to `cmakeFileApiDriver.ts`, `cmakeLegacyDriver.ts`, and `cmakeServerDriver.ts`. Check that subclass overrides are still compatible.\n- **Preset merging**: Changes to `presetsController.ts` or `presetsParser.ts` can alter how presets resolve — verify with nested `include` chains and `CMakeUserPresets.json` overrides.\n- **Settings**: Adding or renaming a setting in `package.json` without updating `src\u002Fconfig.ts` (or vice versa) causes silent failures.\n- **Task provider**: Changes to `cmakeTaskProvider.ts` can break `tasks.json` definitions that users have already configured.\n- **Public API \u002F extensibility**: Changes to exports in `src\u002Fapi.ts` or types in `EXTENSIBILITY.md` can break dependent extensions.\n- **Test coverage**: Flag changes to critical paths that lack corresponding test updates, especially in `src\u002Fdrivers\u002F`, `src\u002Fpresets\u002F`, and `src\u002Fkits\u002F`. See also section 7 (Test Coverage) for detailed test review guidance.\n\n### 6. Adherence to Existing Patterns\n\nVerify the change follows the project's established conventions:\n\n- **Import style**: Uses `@cmt\u002F*` path aliases (not relative paths from outside `src\u002F`). Uses `import * as nls from 'vscode-nls'` for localization.\n- **Logging**: Uses `logging.createLogger('module-name')` — never `console.log`.\n- **Localization**: All user-visible strings use `localize('message.key', 'Message text')` with the `vscode-nls` boilerplate at the top of the file.\n- **Settings access**: Reads settings through `ConfigurationReader` (`src\u002Fconfig.ts`) — never calls `vscode.workspace.getConfiguration()` directly.\n- **Telemetry**: Uses helpers from `src\u002Ftelemetry.ts` — never calls the VS Code telemetry API directly.\n- **Data access**: Uses canonical data paths (e.g., `CMakeProject.targets` for targets, `CMakeDriver.cmakeCacheEntries` for cache) — never parses CMake files or cache directly.\n- **Async patterns**: Prefers `async`\u002F`await` over `.then()` chains (exception: fire-and-forget UI calls).\n- **Naming and structure**: New files are placed in the correct layer directory (see architecture table in `.github\u002Fcopilot-instructions.md`). New commands are registered in `src\u002Fextension.ts`.\n\n### 7. Test Coverage\n\nVerify that the PR includes adequate tests for the changes:\n\n- **New functionality**: Any new function, command, setting, or behavior branch should have corresponding tests. If the change adds a new helper or utility, check that it has unit tests covering its inputs and edge cases.\n- **Bug fixes**: A bug fix should include at least one test that would have caught the original bug — i.e., a test that fails on the base branch and passes with the fix applied.\n- **Changed behavior**: If existing behavior is modified, check that existing tests are updated to reflect the new behavior and that no tests are silently broken or deleted without justification.\n- **Test location**: Unit tests that don't require VS Code APIs belong in `test\u002Funit-tests\u002Fbackend\u002F` and run via `yarn backendTests`. Tests that require VS Code belong in `test\u002Funit-tests\u002F` and run via `yarn unitTests`. Check that new tests are placed in the correct location.\n- **Test quality**: Tests should be specific and descriptive:\n  - Test names should clearly state what is being tested and the expected outcome.\n  - Tests should assert specific values, not just \"no error thrown\".\n  - Tests should cover both positive cases (expected input → expected output) and negative\u002Fedge cases (invalid input, boundary conditions, fallback paths).\n  - Comments in tests should be accurate and not misleading about what the test actually exercises.\n- **Coverage gaps to flag**: Pay special attention to:\n  - Code paths that touch `src\u002Fdrivers\u002F`, `src\u002Fpresets\u002F`, or `src\u002Fkits\u002F` — these are critical and should have test coverage for any non-trivial changes.\n  - Fallback\u002Ferror paths — if the PR adds a fallback (e.g., \"if X fails, try Y\"), both the success and fallback paths should be tested.\n  - Platform-specific branches — if the code branches on `process.platform`, each branch should ideally be covered.\n- **When tests are not feasible**: Some changes (e.g., pure UI wiring, VS Code API integration) are difficult to unit test. In these cases, verify that the manual-checklist or PR description explains how to manually verify the change, and flag the gap rather than ignoring it.\n\n### 8. Documentation Updates\n\nCheck whether the change requires documentation updates:\n\n- **New or changed settings**: Must be reflected in all three locations — `package.json` (`contributes.configuration`), `src\u002Fconfig.ts` (`ConfigurationReader`), and `docs\u002Fcmake-settings.md`.\n- **New commands**: Must be documented in `package.json` (`contributes.commands`) and referenced in the relevant docs page under `docs\u002F`.\n- **User-visible behavior changes**: If the change alters how a feature works (not just fixes a bug), check whether `docs\u002F` pages describing that feature need updating.\n- **Extensibility changes**: If `src\u002Fapi.ts` or public types change, update `EXTENSIBILITY.md`.\n- **README**: If a new major feature is added, check whether `README.md` should mention it.\n\n## Applying This Skill\n\nWhen reviewing or preparing a PR:\n\n1. **Check the title** — rewrite it if it is vague or missing context.\n2. **Check the description** — ensure it explains what, why, and (if needed) how.\n3. **Check `CHANGELOG.md`** — verify an entry exists under the current version in the correct section with the correct format. If missing, add one.\n4. **Check correctness** — review code for logical errors, missing mode\u002Fgenerator handling, cross-platform issues, and error handling gaps.\n5. **Check regression risks** — identify areas where the change could break existing behavior and flag missing test coverage for critical paths.\n6. **Check pattern adherence** — verify the change follows established import, logging, localization, settings access, and architectural conventions.\n7. **Check test coverage** — verify that new or changed behavior has corresponding tests, bug fixes include regression tests, and tests are placed in the correct location with good quality.\n8. **Check documentation** — verify that new or changed settings, commands, and behavior are reflected in the appropriate docs.\n",{"name":5,"description":7},"main","e0969b894e56d8ea5e6641d48a82e5ba3babcc38",".github\u002Fskills\u002Fpr-readiness",559,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-cmake-tools","https:\u002F\u002Faka.ms\u002Fvscode-cmake-tools","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-11 06:52:38",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add microsoft\u002Fvscode-cmake-tools --skill pr-readiness",{"tool":61,"command":62},"bunx","bunx skills add microsoft\u002Fvscode-cmake-tools --skill pr-readiness",{"tool":64,"command":65},"pnpm","pnpm dlx skills add microsoft\u002Fvscode-cmake-tools --skill pr-readiness","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-cmake-tools\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpr-readiness\u002FSKILL.md",true,[69],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"vote-mail-template.md","REFERENCE","参考文档",5654,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fstruts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcreating-release-vote-mail\u002Fvote-mail-template.md",[76,102,121,157,175,192],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":87,"publishedAt":40},"01M69B6J924HHBDH1G30RG9DT3","validation-project","Creates a validation project for testing a specific vscode-cmake-tools pull request. Use this skill when asked to create a validation project, test a PR, validate a pull request, or set up a PR validation environment. The skill creates a structured project directory with documentation, metadata, and checklists for systematically validating PR changes.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-cmake-tools\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fvalidation-project\u002FSKILL.md",[82],{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[88,89,90,91,92,93,39,94,38,19,37,36,95,33,96,97,98,31,99,100,26,101,23],"validation project","validation","project","testing","directory","test","validate","create","SET","Tools","environment","up","with","request",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":109,"publishedAt":40},"01M69B6FDXF7VSNN4VH8MJ2230","presets-vs-kits","Use when writing or reviewing code that must work in both CMake Presets and Kits\u002FVariants modes. Covers configure, build, test, environment, and generator paths. Triggers: \"presets vs kits\", \"useCMakePresets\", \"works in both modes\".","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-cmake-tools\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpresets-vs-kits\u002FSKILL.md",[108],{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},[110,111,93,36,35,112,113,98,31,114,115,116,117,118,119,120,23],"presets vs kits","writing","configure","work","build","triggers","paths","reviewing code","generator","modes","variants",{"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":142,"publishedAt":40},"01M69B69SPZQSR8YNAZMMNERE4","backend-tests","Use when writing unit tests under test\u002Funit-tests\u002Fbackend\u002F*.test.ts that run in Node with Mocha+Chai and no VS Code API. For pure logic: parsers, helpers, env merging. Triggers: \"backend test\", \"unit test\", \"mocha test without vscode\".","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-cmake-tools\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fbackend-tests\u002FSKILL.md",[127,128,131,134,139],{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},{"categoryNo":129,"categoryName":130,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":132,"categoryName":133,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":135,"categoryName":136,"taxonomyType":137,"taxonomyTypeDesc":138},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":140,"categoryName":141,"taxonomyType":137,"taxonomyTypeDesc":138},"01JBSEEDCAT000000000000036","内容创作者",[143,144,145,111,93,39,146,147,35,148,149,150,31,115,151,152,153,154,26,155,23,156],"backend tests","backend","tests","unit tests","run","api","parsers","node","chai","unit","unit-tests","mocha","unit test","helpers",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":40},"01M69B67VACEFYYR745B6WBF4J","add-setting","Use when adding a new cmake.* configuration setting. Touches package.json (contributes.configuration), package.nls.json, src\u002Fconfig.ts (interface + getter), docs\u002Fcmake-settings.md, and CHANGELOG.md. Triggers: \"add setting\", \"new setting\", \"add configuration\".","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-cmake-tools\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fadd-setting\u002FSKILL.md",[],[164,165,166,167,36,34,168,169,170,171,31,172,115,173,23,174],"add setting","add","docs","config","package","src","json","settings","configuration","interface","new",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":40},"01M69B64R9S01TGSH17SSHW9V6","add-diagnostic-parser","Use when adding a compiler or tool output parser for the Problems panel. Touches src\u002Fdiagnostics\u002F\u003Cname>.ts, src\u002Fdiagnostics\u002Fbuild.ts, package.json (cmake.enabledOutputParsers), and package.nls.json. Triggers: \"add parser\", \"new diagnostic parser\", \"parse compiler output\".","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-cmake-tools\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fadd-diagnostic-parser\u002FSKILL.md",[],[182,183,165,184,185,186,36,168,187,169,188,31,114,115,189,190,26,191,23,174],"add diagnostic parser","parser","add diagnostic","diagnostic","diagnostics","compiler","tool","panel","output","parse",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":198,"publishedAt":40},"01M69B622J8838QDVAQMQ0854Z","add-command","Use when adding a new cmake.* command to CMake Tools. Touches package.json (contributes.commands), package.nls.json, src\u002Fextension.ts (funs array), and CHANGELOG.md. Triggers: \"add command\", \"register command\", \"new command palette entry\".","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-cmake-tools\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fadd-command\u002FSKILL.md",[],[199,200,165,36,201,34,168,97,169,170,31,202,115,203,204,205,206,23,174],"add command","command","command palette","commands","extension","register","palette","entry"]