Use when adding a new cmake.* command to CMake Tools. Touches package.json (contributes.commands), package.nls.json, src/extension.ts (funs array), and CHANGELOG.md. Triggers: "add command", "register command", "new command palette entry".
71
87%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Recipe for adding a new cmake.* command to CMake Tools.
| File | What to add |
|---|---|
package.json | Command declaration in contributes.commands + optional menu entries |
package.nls.json | English title string |
src/extension.ts | Method name in funs array + handler method on ExtensionManager |
CHANGELOG.md | Entry under the current version |
package.jsoncontributes.commands// package.json → contributes.commands
{
"command": "cmake.myCommand",
"title": "%cmake-tools.command.cmake.myCommand.title%",
"category": "CMake"
}cmake.<commandName> (camelCase).%cmake-tools.command.cmake.<commandName>.title%."CMake" — this prefixes the title in the Command Palette as CMake: <title>.when (optional): controls when the command appears in the Command Palette.icon (optional): Codicon reference like "$(settings-gear)" for tree-view inline buttons.contributes.menus (if needed)Add visibility rules for where the command appears.
Command Palette visibility:
// package.json → contributes.menus.commandPalette
{
"command": "cmake.myCommand",
"when": "cmake:enableFullFeatureSet"
}Sidebar tree-view inline button:
// package.json → contributes.menus["view/item/context"]
{
"command": "cmake.projectStatus.myCommand",
"when": "view == cmake.projectStatus && cmake:enableFullFeatureSet && viewItem == 'myItem'",
"group": "inline"
}Common when clause patterns:
| Pattern | Meaning |
|---|---|
cmake:enableFullFeatureSet | Extension is fully activated |
useCMakePresets | Presets mode is active |
!useCMakePresets | Kits/variants mode is active |
view == cmake.projectStatus && viewItem == 'kit' | Specific tree-view item |
viewItem =~ /configPreset/ | Regex match on tree-view item |
package.nls.json"cmake-tools.command.cmake.myCommand.title": "My Command Title"For titles containing the product name, use the object form with a translator comment:
"cmake-tools.command.cmake.myCommand.title": {
"message": "Do Something with CMake Tools",
"comment": ["The text 'CMake Tools' should not be localized."]
}Do not modify any file under
i18n/.
src/extension.tsAdd the method name to the funs array (search for const funs: near the end of the file). The register() helper
auto-generates the command ID cmake.<name>, wraps it with debug logging, and hands
the promise to rollbar.takePromise() for error tracking.
// src/extension.ts
const funs: (keyof ExtensionManager)[] = [
// ... existing entries ...
'myCommand', // ← add here
];That's it — no manual registerCommand call needed. The loop that follows handles registration automatically:
for (const key of funs) {
context.subscriptions.push(register(key));
}Only use manual
vscode.commands.registerCommand()for commands that need custom argument handling (e.g., tree-view context-menu commands that receive a node argument). Most commands go through thefunsarray.
ExtensionManagerAdd a method to the ExtensionManager class in src/extension.ts. The method
name must match the string added to the funs array.
myCommand(folder?: vscode.WorkspaceFolder) {
telemetry.logEvent('myCommand');
return this.runCMakeCommand(
cmakeProject => cmakeProject.myCommand(),
folder,
undefined, // precheck (optional)
true // cleanOutputChannel
);
}Then implement the actual logic on CMakeProject in src/cmakeProject.ts.
myCommandAll() {
telemetry.logEvent('myCommand', { all: 'true' });
return this.runCMakeCommandForAll(
cmakeProject => cmakeProject.myCommand()
);
}async myCommand() {
telemetry.logEvent('myCommand');
const result = await vscode.window.showQuickPick(items);
if (!result) {
return;
}
// ... handle result ...
}| Helper | Use when |
|---|---|
this.runCMakeCommand(cmd, folder) | Single-project command |
this.runCMakeCommandForAll(cmd) | Runs on every open CMake project |
this.runCMakeCommandForProject(cmd, project) | Specific project instance |
Add an entry under the current version in CHANGELOG.md, in the Features: section.
package.json — command declared with NLS title and "CMake" categorypackage.json — menu entries added (if applicable) with correct when clausespackage.nls.json — English title string addedsrc/extension.ts — method name added to funs arraysrc/extension.ts — handler method implemented on ExtensionManagertelemetry.logEvent() for telemetryCMakeProject via runCMakeCommand (if project-scoped)CHANGELOG.md — entry addedyarn compile succeedsi18n/ were modifiedSee also: .github/copilot-instructions.md for project-wide conventions.
916baba
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.