vscode-extension-builder-lawvable

Build, bundle, test, and package VS Code extensions into .vsix files.

Updated Apr 6, 2026

Search Tags:#vscode #build #extension #publish #test #bundling #ci

Ready to run

npx skills add https://github.com/joeblackwaslike/agent-skills --skill vscode-extension-builder-lawvable

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vscode-extension-builder-lawvable
Source: https://github.com/joeblackwaslike/agent-skills/tree/main/skills/vscode-extension-builder-lawvable
Command: npx skills add https://github.com/joeblackwaslike/agent-skills --skill vscode-extension-builder-lawvable

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the need to manage the full lifecycle of VS Code extension development—scaffolding, bundling, testing, packaging, and publishing—so developers can deliver reliable extensions faster.

Core Features & Use Cases

End-to-end extension lifecycle tooling: scaffold new extensions, configure builds, run tests, package into .vsix, and publish to the marketplace.
Supports extension host, webview, and packaging considerations for both browser and desktop environments.
CI-friendly workflows with deterministic builds, type checks, and artifact generation for release pipelines.

Quick Start

Use the vscode-extension-builder-lawvable to scaffold, bundle, test, and publish a new VS Code extension.

Frequently Asked Questions about vscode-extension-builder-lawvable

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I build and publish a VS Code extension from start to finish?▼

To build and publish a VS Code extension, you scaffold the project, configure esbuild or webpack, run tests, package the code into a .vsix file, and execute the VS Code publishing steps to the marketplace.

What is the best way to bundle a VS Code extension for the marketplace?▼

The best way to bundle a VS Code extension is using esbuild or webpack workflows to compile TypeScript and optimize assets. This ensures deterministic builds and proper artifact generation for both browser and desktop environments.

Can I use this VS Code extension builder for webview and extension host projects?▼

Yes, this VS Code extension builder supports packaging considerations for both extension host and webview projects. It handles the distinct requirements for browser and desktop environments across the full development lifecycle.

How do I set up CI workflows for VS Code extension testing and packaging?▼

You set up CI workflows for VS Code extension testing by integrating deterministic builds, type checks, and automated test runs. This Skill provides CI-friendly workflows that generate release artifacts for your deployment pipelines.

Does building VS Code extensions with esbuild require TypeScript?▼

Yes, building VS Code extensions with esbuild requires TypeScript. This Skill applies TypeScript alongside esbuild and webpack workflows to compile, bundle, and package your extension code for distribution.