build-extension
Skill5 starsChanged 23 days agoMITView on GitHub
Build, package, and install the Agntree VS Code extension. Use when asked to build, compile, package, create a VSIX, or install/update the extension.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- MelbourneDeveloper/dart_nodetheir own version, first seen Oct 9, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- MelbourneDeveloper/dart_node★ 113same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- add-featureSkill
- debug-extensionSkill
- inspect-runtime-stateSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 35
Read the version from package.json rather than assuming one.
- Very specific: line 43
No need to uninstall the existing copy first.
- Very specific: line 47
If code is not found, the user has to run the command themselves.
- Distinctive: line 52
After installing, always tell the user to reload the window:
- Distinctive: line 63
Check the installed files rather than re-packaging:
- Very specific: line 70
If the timestamp is current, the install succeeded and only the reload is missing.
- Distinctive: line 81
Test in VS Code
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Build Extension
Build, package, and install the Agntree VS Code extension. Run these from the repository root.
Build
npm run compileThis bundles src/ into out/extension.js with esbuild. Fix any errors before packaging.
Optionally type-check and run the fast tests:
npm run typecheck
npm run test:dryPackage as VSIX
npx @vscode/vsce package --allow-missing-repositoryThe output is agntree-<version>.vsix in the repo root (for example agntree-1.2.1.vsix).
Read the version from package.json rather than assuming one.
Install the Extension
code --install-extension ./agntree-<version>.vsix --force- No need to uninstall the existing copy first.
--forcereplaces it in place, even when the version number is unchanged (the usual case during local development). - Reinstalling keeps repositories and sessions: the extension ID is unchanged, so
globalState(stored per extension ID) survives. - If
codeis not found, the user has to run the command themselves; suggest they prefix it with!in the prompt so the output lands in the conversation.
Reload VS Code — tell the user
After installing, always tell the user to reload the window:
VS Code loads extensions at startup. Installing from the CLI writes the new files but the open window keeps running the old code. Run Developer: Reload Window from the Command Palette (
Cmd+Shift+P), or quit and reopen VS Code.
There is no CLI command that reloads a specific running window, so this step cannot be done for them. Do not report the change as visible until they have reloaded.
Verify the install (when the user says they see no changes)
Check the installed files rather than re-packaging:
node -p "require('./package.json').publisher + '.' + require('./package.json').name + '@' + require('./package.json').version"
ls -l ~/.vscode/extensions/<publisher>.<name>-<version>/out/extension.jsIf the timestamp is current, the install succeeded and only the reload is missing. For
VS Code Insiders the directory is under ~/.vscode-insiders/extensions; for other forks
use that fork's code CLI.
Development Workflow
- Make changes to source files in
src/ npm run compileto check for errors- Package with
npx @vscode/vsce package --allow-missing-repository - Install with
code --install-extension ./agntree-<version>.vsix --force - Tell the user to reload: Command Palette (
Cmd+Shift+P) → Developer: Reload Window - Test in VS Code
Troubleshooting
- Compile errors: read the esbuild output;
npm run typecheckgives the full diagnostics. - Packaging failures: run
npm installfirst. The--allow-missing-repositoryflag is needed because this is a local project without a public repository URL. - "Extension is already installed": add
--force. - Changes not visible after install: the window was not reloaded — see the section above.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

