agentleFS
soumatheusgomessoumatheusgomes/agentville/.claude/skills/release-vsix/SKILL.md

release-vsix

Skill9 starsChanged 3 months agoApache-2.0View on GitHub

Package this VS Code extension into an installable .vsix. Use when asked to "gerar nova versão da extensão", "nova release", "release the extension", "package/build the vsix", "empacotar a extensão", or "ship it". Runs `npm run package` (patch bump + minified esbuild build + vsce package), guards bundle size, and reports the artifact.

The file

Files
SKILL.md

release-vsix

Package the extension for distribution as a .vsix.

Publishing to the store is not this skill. A real release goes through gh workflow run release.yml -f bump=patch (verify → bump → package → Open VSX → push → GitHub Release) — see docs/PUBLISHING.md. Use this skill for local builds and testing only.

Steps

  1. Clean tree — git status. The package script bumps the patch version in package.json, so commit or stash unrelated changes first, or they get mixed in.
  2. Verify before shipping:
    npm run lint && npx tsc --noEmit && npm run test
  3. Check .vscodeignore excludes everything that must not ship. Only dist/, package.json, readme.md, and LICENSE.txt belong in the bundle. Any dev/harness directory added since the last release (e.g. .claude/, vault-obsidian/, graphify-out/, .github/, docs/, scripts/, and root files like CLAUDE.md, .mcp.json, .lsp.json) must be listed in .vscodeignore, or vsce packs it. ⚠️ .claude/scripts/node_modules/ alone carries a ~243 MB SDK binary — a stale .vscodeignore produced a 77 MB / 3000-file bundle once.
  4. Package:
    npm run package
    Removes any old *.vsix, bumps the patch version (npm version patch --no-git-tag-version), builds the minified bundle (vscode:prepublish → node esbuild.js --minify), and produces agentville-<version>.vsix at the repo root.
  5. Guard the size — read the vsce summary. A healthy bundle is a handful of files and tens of KB. If it reports MBs or hundreds of files, a directory leaked: add it to .vscodeignore, git checkout -- package.json package-lock.json to undo the bump, and re-run step 4 (so the version only advances once).
  6. Report the generated .vsix filename, its size/file-count, and the new version.
  7. Remind to install + reload:

    code --install-extension agentville-<version>.vsix --force
    # or Antigravity: antigravity-ide --install-extension <file> --force

    Then Command Palette → Developer: Reload Window.

Notes

  • The version bump is not committed automatically — review and commit package.json (and package-lock.json) after packaging. The .vsix itself is gitignored.
  • For a clean upgrade instead of --force, the bumped version alone is enough.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.