How do I install the Vscode Release skill?

Run npx skillmds@latest add tomevault-io/vscode-release 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 Release safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Vscode Release?

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 Release free to use?

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

Who published Vscode Release?

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

Vscode Release by tomevault-io — Agent Skill

Name: Vscode Release
Author: tomevault-io

Vscode Release

Execute the VS Code extension release workflow when the user asks to publish/release the difit VS Code extension. Run local VSIX build and smoke verification first, ask for explicit OK in Japanese, then publish with vsce. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

VS Code Extension Release Workflow

Follow this workflow for the current repository.

Prepare local build verification

Verify release target files in packages/vscode and confirm current branch state.
Run pnpm install --frozen-lockfile.
Run pnpm -C packages/vscode run package.
Read packages/vscode/package.json and confirm the current extension version.
Confirm the VSIX exists at packages/vscode/difit-vscode-<version>.vsix.
Ask the user to smoke test the local VSIX install in VS Code:
- Install from VSIX.
- Confirm the difit command opens review correctly.
- Confirm the toolbar button/icon appears and works.
Ask for explicit OK in Japanese before publishing.

Release after explicit OK

Treat the locally verified build result at OK time as the source of truth. Do not skip rebuilding after version changes.

Bump extension version in packages/vscode/package.json:
- pnpm -C packages/vscode version patch --no-git-tag-version
Re-run pnpm -C packages/vscode run package and confirm the new VSIX filename.
Commit packages/vscode/package.json with an English message: chore(vscode): release vX.Y.Z.
Create tag vscode-vX.Y.Z.
Push main and tags: git push origin main --tags.
If push is rejected by non-fast-forward:
- Run git pull --rebase origin main.
- Retry git push origin main --tags.
Publish to Visual Studio Marketplace:
- pnpm -C packages/vscode exec vsce publish
- Use the already bumped version from packages/vscode/package.json.

Output to user

Respond in Japanese.
Report local build verification result, released version, created tag, and publish result.
Mention if any recovery step was required (for example, rebase due to non-fast-forward).

Source: yoshiko-pg/difit — distributed by TomeVault.

---name: vscode-releasedescription: Execute the VS Code extension release workflow when the user asks to publish/release the difit VS Code extension. Run local VSIX build and smoke verification first, ask for explicit OK in Japanese, then publish with vsce. Use when this capability is needed.---# VS Code Extension Release WorkflowFollow this workflow for the current repository.## Prepare local build verification1. Verify release target files in `packages/vscode` and confirm current branch state.2. Run `pnpm install --frozen-lockfile`.3. Run `pnpm -C packages/vscode run package`.4. Read `packages/vscode/package.json` and confirm the current extension version.5. Confirm the VSIX exists at `packages/vscode/difit-vscode-<version>.vsix`.6. Ask the user to smoke test the local VSIX install in VS Code: - Install from VSIX. - Confirm the `difit` command opens review correctly. - Confirm the toolbar button/icon appears and works.7. Ask for explicit OK in Japanese before publishing.## Release after explicit OKTreat the locally verified build result at OK time as the source of truth. Do not skip rebuilding after version changes.1. Bump extension version in `packages/vscode/package.json`: - `pnpm -C packages/vscode version patch --no-git-tag-version`2. Re-run `pnpm -C packages/vscode run package` and confirm the new VSIX filename.3. Commit `packages/vscode/package.json` with an English message: `chore(vscode): release vX.Y.Z`.4. Create tag `vscode-vX.Y.Z`.5. Push `main` and tags: `git push origin main --tags`.6. If push is rejected by non-fast-forward: - Run `git pull --rebase origin main`. - Retry `git push origin main --tags`.7. Publish to Visual Studio Marketplace: - `pnpm -C packages/vscode exec vsce publish` - Use the already bumped version from `packages/vscode/package.json`.## Output to user- Respond in Japanese.- Report local build verification result, released version, created tag, and publish result.- Mention if any recovery step was required (for example, rebase due to non-fast-forward).---> Source: [yoshiko-pg/difit](https://github.com/yoshiko-pg/difit) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions