How do I install the Vscode Extension Workflow skill?

Run npx skillmds@latest add tomevault-io/vscode-extension-workflow in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Vscode Extension Workflow safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Vscode Extension Workflow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Vscode Extension Workflow free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Vscode Extension Workflow?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Vscode Extension Workflow by tomevault-io

Name: Vscode Extension Workflow
Author: tomevault-io

File contents

Use this skill when working on workflows or commands for this repo's VS Code extension.

Shared conventions

Follow AGENTS.md for coding style, TypeScript/lint rules, testing conventions, and shared engineering constraints.
Keep this skill focused on workflow/packaging/command concerns.

Key files

package.json for scripts, activation events, and contributions.
src/extension.ts for activation and command wiring.
src/integratedTreeProvider.ts for Filter/View controls tree UI.
src/searchViewProvider.ts for webview-side filter/search/history interactions.
README.md for user-visible docs and command lists.
eslint.config.js for ESLint 9 flat-config rules.

Commands

Install deps: npm install
Bundle (dev): npm run esbuild
Bundle (minified): npm run vscode:prepublish
Type check: npm run compile
Lint: npm run lint
Tests: npm test

Single test

Prefer VS Code Testing view; tests are discovered in src/test/ (*.test.ts).
CLI: npm test -- --grep "<test name substring>".

Workflow checklist

Update package.json commands or contributions as needed.
Keep README.md in sync with new commands or settings.
Avoid editing generated output in out/ or dist/.
Match existing TypeScript style and ESLint rules.
Run npm run compile, npm run lint, and npm test after changes when feasible.
Keep docs DRY: reference package.json as command/settings source of truth.
Follow AGENTS.md for design-first, SOLID/DRY, and minimal-change guidance when changing scripts/contributions.
Avoid unnecessary refactors of scripts/contributions; keep workflow edits minimal and focused.

Feature/workflow hotspots

Filter controls now support per-field modes (Contains/Regex/Glob) and recent-filter operations.
Custom view flows include select/apply/toggle/import/export plus workspace/global storage scope (see custom-views.md for schema and constraints).
Performance behavior includes refreshMode, debounceDelay, and adaptiveDebounce settings.
Search and saved filters use persistent stores (SearchHistoryStore, SavedFiltersStore).

Gotchas

The extension activates on onLanguage:arxml.
Additional activation occurs for views (arxml-integrated-view, bookmark-tree-view).
ESLint uses flat config (eslint.config.js), not legacy eslintrc files.
Tests are Mocha-based and executed via the VS Code test runner.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: vscode-extension-workflowdescription: Build, lint, test, and package this VS Code extension. Use when changing extension commands, activation, packaging, or build/test scripts. Use when this capability is needed.---Use this skill when working on workflows or commands for this repo's VS Code extension.Shared conventions- Follow [`AGENTS.md`](../../../AGENTS.md) for coding style, TypeScript/lint rules, testing conventions, and shared engineering constraints.- Keep this skill focused on workflow/packaging/command concerns.Key files- [`package.json`](../../../package.json) for scripts, activation events, and contributions.- [`src/extension.ts`](../../../src/extension.ts) for activation and command wiring.- [`src/integratedTreeProvider.ts`](../../../src/integratedTreeProvider.ts) for Filter/View controls tree UI.- [`src/searchViewProvider.ts`](../../../src/searchViewProvider.ts) for webview-side filter/search/history interactions.- [`README.md`](../../../README.md) for user-visible docs and command lists.- [`eslint.config.js`](../../../eslint.config.js) for ESLint 9 flat-config rules.Commands- Install deps: `npm install`- Bundle (dev): `npm run esbuild`- Bundle (minified): `npm run vscode:prepublish`- Type check: `npm run compile`- Lint: `npm run lint`- Tests: `npm test`Single test- Prefer VS Code Testing view; tests are discovered in [`src/test/`](../../../src/test/) (`*.test.ts`).- CLI: `npm test -- --grep "<test name substring>"`.Workflow checklist1. Update [`package.json`](../../../package.json) commands or contributions as needed.2. Keep [`README.md`](../../../README.md) in sync with new commands or settings.3. Avoid editing generated output in `out/` or `dist/`.4. Match existing TypeScript style and ESLint rules.5. Run `npm run compile`, `npm run lint`, and `npm test` after changes when feasible.6. Keep docs DRY: reference [`package.json`](../../../package.json) as command/settings source of truth.7. Follow [`AGENTS.md`](../../../AGENTS.md) for design-first, SOLID/DRY, and minimal-change guidance when changing scripts/contributions.8. Avoid unnecessary refactors of scripts/contributions; keep workflow edits minimal and focused.Feature/workflow hotspots- Filter controls now support per-field modes (Contains/Regex/Glob) and recent-filter operations.- Custom view flows include select/apply/toggle/import/export plus workspace/global storage scope (see [`custom-views.md`](../arxml-tree-domain/references/custom-views.md) for schema and constraints).- Performance behavior includes `refreshMode`, `debounceDelay`, and `adaptiveDebounce` settings.- Search and saved filters use persistent stores (`SearchHistoryStore`, `SavedFiltersStore`).Gotchas- The extension activates on `onLanguage:arxml`.- Additional activation occurs for views (`arxml-integrated-view`, `bookmark-tree-view`).- ESLint uses flat config ([`eslint.config.js`](../../../eslint.config.js)), not legacy eslintrc files.- Tests are Mocha-based and executed via the VS Code test runner.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/robinbreast) — claim your Tome and manage your conversions.

Frequently asked questions

Vscode Extension Workflow