Skip to content

Commit f69660c

Browse files
committed
add skills for adding commands, diagnostic parsers, settings, backend tests, and handling presets vs kits
1 parent 9c1d2b0 commit f69660c

File tree

5 files changed

+42
-0
lines changed

5 files changed

+42
-0
lines changed
Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,11 @@
1+
---
2+
name: add-command
3+
description: >
4+
Use when adding a new cmake.* command to CMake Tools. Touches package.json
5+
(contributes.commands), package.nls.json, src/extension.ts (funs array), and
6+
CHANGELOG.md. Triggers: "add command", "register command", "new command palette entry".
7+
---
8+
19
# Adding a New Command
210

311
Recipe for adding a new `cmake.*` command to CMake Tools.

.github/prompts/add-diagnostic-parser.prompt.md renamed to .github/skills/add-diagnostic-parser/SKILL.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,12 @@
1+
---
2+
name: add-diagnostic-parser
3+
description: >
4+
Use when adding a compiler or tool output parser for the Problems panel. Touches
5+
src/diagnostics/<name>.ts, src/diagnostics/build.ts, package.json
6+
(cmake.enabledOutputParsers), and package.nls.json. Triggers: "add parser",
7+
"new diagnostic parser", "parse compiler output".
8+
---
9+
110
# Adding a New Diagnostic / Output Parser
211

312
Recipe for adding a new compiler or tool output parser to CMake Tools. A parser extracts diagnostics (errors, warnings, notes) from build output and surfaces them in the VS Code **Problems** panel.
Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,12 @@
1+
---
2+
name: add-setting
3+
description: >
4+
Use when adding a new cmake.* configuration setting. Touches package.json
5+
(contributes.configuration), package.nls.json, src/config.ts (interface + getter),
6+
docs/cmake-settings.md, and CHANGELOG.md. Triggers: "add setting", "new setting",
7+
"add configuration".
8+
---
9+
110
# Adding a New Configuration Setting
211

312
Recipe for adding a new `cmake.*` setting to CMake Tools.

.github/prompts/write-backend-test.prompt.md renamed to .github/skills/backend-tests/SKILL.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,11 @@
1+
---
2+
name: backend-tests
3+
description: >
4+
Use when writing unit tests under test/unit-tests/backend/*.test.ts that run in
5+
Node with Mocha+Chai and no VS Code API. For pure logic: parsers, helpers, env
6+
merging. Triggers: "backend test", "unit test", "mocha test without vscode".
7+
---
8+
19
# Writing Backend Tests
210

311
Recipe for adding backend (unit) tests that run without VS Code.
Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,11 @@
1+
---
2+
name: presets-vs-kits
3+
description: >
4+
Use when writing or reviewing code that must work in both CMake Presets and
5+
Kits/Variants modes. Covers configure, build, test, environment, and generator
6+
paths. Triggers: "presets vs kits", "useCMakePresets", "works in both modes".
7+
---
8+
19
# Presets Mode vs Kits/Variants Mode
210

311
Guide for writing code that works correctly in **both** operating modes of CMake Tools. Any shared code path (configure, build, test, environment, targets) **must** handle both modes.

0 commit comments

Comments
 (0)