[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ACJERGEM6AYZGCC6A2ZC27":3,"skill-same:01M6ACJERGEM6AYZGCC6A2ZC27":74},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M6ACJERGEM6AYZGCC6A2ZC27","creating-release-vote-mail",null,"Use when opening the formal release vote for a Struts release candidate on any maintenance line (6.x, 7.x) - composing and drafting the [VOTE] Apache Struts X.Y.Z mail to dev@ once the Version Notes page, GitHub release and staged artifacts are published.","apache\u002Fstruts","apache","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F47359?v=4","01M6AC83E6K4FDKK7HZ8WNMQKE","The Apache Software Foundation","01M6ACJC9PH86ZGJ487XPD32BP",1373,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fapache\u002Fstruts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcreating-release-vote-mail\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,9,35,36,37],"release","creating release vote mail","mail","use","drafting","when","candidate","staged","for","line","maintenance","version","github","page","github release","struts","dev","artifacts","notes","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":43,"description":44},"pr-readiness","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.","main","e0969b894e56d8ea5e6641d48a82e5ba3babcc38",".claude\u002Fskills\u002Fcreating-release-vote-mail",876,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fstruts","https:\u002F\u002Fstruts.apache.org\u002F","https:\u002F\u002Fgithub.com\u002Fapache","https:\u002F\u002Fwww.apache.org\u002F","2026-11-14 17:00:41",{"source":8,"skillName":43,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add apache\u002Fstruts --skill pr-readiness",{"tool":60,"command":61},"bunx","bunx skills add apache\u002Fstruts --skill pr-readiness",{"tool":63,"command":64},"pnpm","pnpm dlx skills add apache\u002Fstruts --skill pr-readiness","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fapache\u002Fstruts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcreating-release-vote-mail\u002FSKILL.md",true,[68],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"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",[75,113,137,151,171,183],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":94,"publishedAt":38},"01M6ACJVHR7YZNC8AZFK987QP0","code-review","Apache Struts pull request review guide. Use when reviewing pull requests in this repository to check test conventions, security-sensitive framework code, PR and commit hygiene, and Struts-specific implementation patterns.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fstruts\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcode-review\u002FSKILL.md",[81,86,89],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":87,"categoryName":88,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[95,96,97,98,99,100,9,101,102,34,103,104,105,106,107,22,108,24,109,110,111,112],"code review","code","review","pull","pull requests","test","pr","pull request","security","commit","framework","Test Conventions","review guide","pull request review","check","requests","request","repository",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":122,"publishedAt":38},"01M6ACJSK2MWX4MPVHH4S3FK0V","triaging-security-reports","Use when a vulnerability or security report arrives for triage, when assessing a CVE\u002FRCE\u002FOGNL\u002Finjection claim against the code, when deciding whether a finding is the framework's fault or the application's, when drafting a reply to a security researcher, or when a claim that is already public (a Full Disclosure post, a blog, a scanner advisory) needs the project's position stated for users and scanner vendors — to research the claim from source without trusting the reporter and without fabricating your own facts.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fstruts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftriaging-security-reports\u002FSKILL.md",[119],{"categoryNo":120,"categoryName":121,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000021","资料检索与研究",[123,103,124,96,125,27,126,127,22,128,129,130,131,132,24,133,134,105,135,136,23],"triaging security reports","reports","cve","security report","claim","vulnerability","facts","injection","source","project","scanner","full","advisory","users",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":38},"01M6ACJQJRMWRPQJ7P796RJZDZ","releasing-struts","Use when running or planning an Apache Struts release on any maintenance line (6.x, 7.x) - cutting the tag, staging artifacts, opening the vote, promoting, updating the site and announcing - or when asked what the next step in a release is.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fstruts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Freleasing-struts\u002FSKILL.md",[],[34,144,9,145,36,19,146,22,24,29,147,148,28,149,150],"releasing struts","planning","running","next","what the","site","next step",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":38},"01M6ACJNFT2MMYBT8WFBJR8HXM","merging-dependabot-prs","Use when triaging, classifying or landing Dependabot pull requests in this repo — clearing the open Dependabot queue, deciding whether a bump needs a WW Jira ticket, or checking whether a bump's build actually passed.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fstruts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmerging-dependabot-prs\u002FSKILL.md",[],[158,159,160,98,99,161,162,163,164,165,166,22,24,110,167,168,169,170],"merging dependabot prs","prs","dependabot","jira","bump","repo","landing","ticket","open","build","ww","queue","jira ticket",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":177,"publishedAt":38},"01M6ACJK00H307C0B4HTMM34EB","creating-version-notes","Use when preparing, updating, or reviewing the release documentation for a Struts release or release candidate on any maintenance line (6.x, 7.x) - the Version Notes page on the cwiki, its Migration Guide entry, the GitHub release notes, and the test-build announcement mail.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fstruts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcreating-version-notes\u002FSKILL.md",[],[37,178,30,179,100,180,31,19,181,34,24,25,21,28,182,33,27,32,22,29],"creating version notes","documentation","announcement","release notes","guide",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":189,"publishedAt":38},"01M6ACJGZAS1WB8RHDQMC76XFB","creating-security-bulletins","Use when drafting, updating, or reviewing an S2-XXX security bulletin on the Struts cwiki, when preparing bulletin text ahead of a CVE request, when filling a CVE record in the ASF CVE tool (cveprocess.apache.org \u002F Vulnogram), when deciding when to publish, when publishing a bulletin and announcing it to the ASF lists, when wrapping up after the advisory mails, or when deciding how much detail about a fixed vulnerability is safe to publish.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fstruts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcreating-security-bulletins\u002FSKILL.md",[],[103,190,34,9,191,192,24,23,128,193,194,195,111,196,197,125,198,199,22,200],"creating security bulletins","safe","up","text","publish","how","asf","org","tool","publishing","detail"]