New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Vscode Release

by yoshiko-pg in yoshiko-pg/difit

Execute the VS Code extension release workflow when the user asks to publish/release the difit VS Code extension.

MITAuto-check passedDevelopment

Install Vscode Release

skills CLI
$ npx skills add yoshiko-pg/difit --skill vscode-release -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install yoshiko-pg/difit vscode-release --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/yoshiko-pg/difit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/vscode-release .claude/skills/vscode-release && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
vscode-release
GitHub stars
3.2k
Token cost
~518 tokens
SKILL.md length
239 words
Files
2
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

Execute the VS Code extension release workflow when the user asks to publish/release the difit VS Code extension.

  • Works in 7 steps: Verify release target files in… → Run pnpm install --frozen-lockfile. → Run pnpm -C packages/vscode run package. → …
  • Asks to publish/release the difit VS Code extension
  • SKILL.md covers Prepare local build verification, Release after explicit OK and Output to user
  • Calls pnpm and git

What it does

Vscode Release is an agent skill from yoshiko-pg/difit. 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.

Its SKILL.md is about 520 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Development. It works with Visual Studio Code, pnpm, Git and npm. The repository describes itself as: A lightweight command-line tool that spins up a local web server to display Git commit diffs in a GitHub-like Files changed view. The licence is MIT.

When your agent uses it

  • Asks to publish/release the difit VS Code extension

Example prompts

  • “/vscode-release”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. 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-.vsix.
  6. Ask the user to smoke test the local VSIX install in VS Code
  7. Ask for explicit OK in Japanese before publishing.

What it can do on your machine

Read from SKILL.md and the folder at commit 82a765c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pnpm
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pnpm and git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Vscode Release loads about 518 tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 239 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~59
When it runs · the whole SKILL.md, loaded when a task matches
~518

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from yoshiko-pg/difit at commit 82a765c, republished under its MIT licence (© yoshiko-pg). 239 words, ~518 tokens.

Download SKILL.mdSave it as .claude/skills/vscode-release/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
vscode-release
description
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.
metadata.internal
true

VS Code Extension Release Workflow

Follow this workflow for the current repository.

Prepare local build verification

  1. 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 OK

Treat 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).

© yoshiko-pg, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .codex/skills/vscode-release of yoshiko-pg/difit.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 82a765c

Compare with similar skills

Vscode Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Vscode Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vscode Release this skillyoshiko-pg/difit3.2k—~518Automated safety check: PassMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT
ZCF Release AutomationUfoMiao/zcf6.1k—~3.4kAutomated safety check: PassMIT
Release Clawpatchopenclaw/clawpatch813—~1.1kAutomated safety check: PassMIT
Antfuoyjt/uniapp-vue3-template627—~1.3kAutomated safety check: PassMIT
Releasecyanfish-x/tellux207—~1.3kAutomated safety check: PassMIT

Similar skills

  • Verdaccio Pull Request Workflow

    verdaccio/verdaccio

    Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

  • ZCF Release Automation

    UfoMiao/zcf

    Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.

    6.1k GitHub stars~3.4k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Release Clawpatch

    openclaw/clawpatch

    clawpatch release: version/changelog, CI, npm publish, GitHub release, verify.

    813 GitHub stars~1.1k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Antfu

    oyjt/uniapp-vue3-template

    Anthony Fu's {Opinionated} preferences and best practices for web development

    627 GitHub stars~1.3k tokensUpdated 4 mo ago
    DevelopmentAuto-check passed

  • Release

    cyanfish-x/tellux

    Cut and publish a new tellux release — bump version, curate a changelog summary from recent commits, pause for the user to manually pnpm publish (browser 2FA), then push the tag and create the…

    207 GitHub stars~1.3k tokensUpdated 18 days ago
    DevelopmentAuto-check passed

  • Package Patch Release

    swjybky/deepwrite

    为 DeepWrite 桌面端递增一个 SemVer 补丁版本，安全清理上一个版本的测试打包残留，使用项目规定的 pnpm pack:test 命令构建并验证新安装包，按用户要求决定是否创建并发布 GitHub Release；Release 完整可下载后更新根目录 update.json，并通过路径限定提交和推送，保证该提交只包含…

    586 GitHub stars~1.2k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from yoshiko-pg/difit

  • Difit

    yoshiko-pg/difit

    Ask the user for a code review by opening the changes in difit, a local diff viewer.

    3.2k GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed

  • Difit Review

    yoshiko-pg/difit

    A skill for reviewing a specific diff and showing the findings as comments inside difit (the diff viewer).

    3.2k GitHub stars~764 tokensUpdated 1 mo ago
    Auto-check passed

  • Difit Review

    yoshiko-pg/difit

    Review a specific diff (branch, commit, or GitHub PR) and show the findings as comments inside difit, the local diff viewer.

    3.2k GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed

  • Difit Dev

    yoshiko-pg/difit

    Ask the user for a code review through difit after code changes in this repository, using pnpm run dev.

    3.2k GitHub stars~708 tokensUpdated 1 mo ago
    Auto-check passed

  • Release

    yoshiko-pg/difit

    Execute the difit release workflow when the user says "リリース" or asks to cut a release.

    3.2k GitHub stars~688 tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Vscode Release

What does Vscode Release do?

Execute the VS Code extension release workflow when the user asks to publish/release the difit VS Code extension. Vscode Release is an agent skill from yoshiko-pg/difit. Execute the VS Code extension release workflow when the user asks to publish/release the difit VS Code extension.

When should I use Vscode Release?

Vscode Release fits situations like: asks to publish/release the difit VS Code extension.

How do I install Vscode Release in Claude Code?

Run `npx skills add yoshiko-pg/difit --skill vscode-release -a claude-code`. Or copy the skill folder (.codex/skills/vscode-release in yoshiko-pg/difit) into .claude/skills/vscode-release in your project. Claude Code loads it when a task matches its description.

How do I install Vscode Release in Codex?

Run `npx skills add yoshiko-pg/difit --skill vscode-release -a codex`. Or copy the skill folder (.codex/skills/vscode-release in yoshiko-pg/difit) into .agents/skills/vscode-release in your project. Codex loads it when a task matches its description.

Can I use Vscode Release in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yoshiko-pg/difit --skill vscode-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vscode-release, .gemini/skills/vscode-release, .github/skills/vscode-release and .opencode/skills/vscode-release in your project.

What does Vscode Release need to run?

Going by SKILL.md and its folder, Vscode Release needs the command-line tools its instructions call (pnpm and git).

Does Vscode Release access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Vscode Release safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Vscode Release use?

Vscode Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Vscode Release use?

About 518 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Vscode Release?

Skills that share tags, products or a category with Vscode Release: Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), ZCF Release Automation (UfoMiao/zcf, 6.1k stars), Release Clawpatch (openclaw/clawpatch, 813 stars) and Antfu (oyjt/uniapp-vue3-template, 627 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vscode Release?

yoshiko-pg (a GitHub user) maintains it in yoshiko-pg/difit, which has 3,239 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on August 28, 2026.

Source: yoshiko-pg/difit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.