New: 97,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

Release

by forcedotcom in forcedotcom/salesforcedx-vscode

Run the VS Code extension release workflow end-to-end. An agent skill from forcedotcom/salesforcedx-vscode.

BSD-3-ClauseAuto-check passedDevelopment

Install Release

skills CLI
$ npx skills add forcedotcom/salesforcedx-vscode --skill release -a claude-code

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

GitHub CLI
$ gh skill install forcedotcom/salesforcedx-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/forcedotcom/salesforcedx-vscode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/release .claude/skills/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
release
GitHub stars
1k
Token cost
~1.7k tokens
SKILL.md length
634 words
Files
1
Skills in repo
37
Repo updated
First seen
Licence
BSD-3-Clause

At a glance

Run the VS Code extension release workflow end-to-end. An agent skill from forcedotcom/salesforcedx-vscode.

  • Works in 5 steps: Download stable release build → Install and test locally → Confirm manual testing is complete → …
  • Publishing a release
  • SKILL.md covers Step 1 — Download stable…, Step 2 — Install and test…, Step 3 — Confirm manual… and Step 4 — Promote the release,…, plus 3 more sections
  • Calls gh; reaches marketplace.visualstudio.com

What it does

Release is an agent skill from forcedotcom/salesforcedx-vscode. Run the VS Code extension release workflow end-to-end. Use when publishing a release, running prerelease, verifying the release branch, polishing changelog for release, or installing release vsixes for verification.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Changelog and release notes. It works with Visual Studio Code, Slack and GitHub. The repository describes itself as: Salesforce Extensions for VS Code. The licence is BSD-3-Clause.

When your agent uses it

  • Publishing a release
  • Running prerelease
  • Verifying the release branch
  • Polishing changelog for release

Example prompts

  • “/release”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Download stable release build
  2. Install and test locally
  3. Confirm manual testing is complete
  4. Promote the release, then trigger marketplace publish
  5. Slack post

What it can do on your machine

Read from SKILL.md and the folder at commit f7bb6fe. 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:

    • gh

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • marketplace.visualstudio.com

    Also links to:

    • salesforce.enterprise.slack.com
    • open-vsx.org

    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

Release loads about 1.7k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 634 words of instructions outside code blocks.

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

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 forcedotcom/salesforcedx-vscode at commit f7bb6fe, republished under its BSD-3-Clause licence (© forcedotcom). 634 words, ~1,667 tokens.

Download SKILL.mdSave it as .claude/skills/release/SKILL.md (or your agent's skills folder).
name
release
description
Run the VS Code extension release workflow end-to-end. Use when publishing a release, running prerelease, verifying the release branch, polishing changelog for release, or installing release vsixes for verification.
review
never

Release Workflow

Full doc: contributing/publishing.md

Step 1 — Download stable release build

Get VSIX + SHA256 from GitHub pre-release created by build-github-release.yml. Release notes link to docs/release-testing-guide.md for full testing/publishing instructions:

sh
gh release list --repo forcedotcom/salesforcedx-vscode | head -5
gh release download v<version> \
  --dir ~/Downloads/v<version> \
  --pattern '*.vsix' \
  --repo forcedotcom/salesforcedx-vscode

Step 2 — Install and test locally

Ask user: code or code-insiders? (default code)

sh
find ~/Downloads/v<version> -type f -name "*.vsix" -exec <binary> --install-extension {} \;

User should reload VS Code and run a few commands to validate.

Step 3 — Confirm manual testing is complete

3a — Create the Slack testing doc

The user creates the testing doc from the team's Slack template: https://salesforce.enterprise.slack.com/docs/T092Z56AE/F0B7RLRUSRG

Create a new doc from the Slack template and name it Release Testing v<version> (e.g. Release Testing v67.12.0), where <version> matches the GH release tag.

Use the version from Step 1. Wait for the user to confirm the doc is created and shared with the team before continuing.

3b — Run smoke checks

Tell the user: "Let me know when you've finished manually testing the installed vsixes (logged in the Slack doc) and you're ready to publish to the Microsoft Marketplace and Open VSX."

Suggested smoke checks the user may run before confirming:

  • Authorize an org / set a default org
  • Deploy and retrieve metadata
  • Run an Apex test from the Test Explorer
  • Open SOQL Builder and run a query
  • Open the Org Browser

Do not proceed until the user explicitly confirms testing is complete.

Step 4 — Promote the release, then trigger marketplace publish

Once user confirms testing is complete, first promote the GitHub release from pre-release to a full release — this is the actual "make it stable" signal, and it's required before vsce publish will accept the VSIX. The publish pipeline reads the release's isPrerelease flag and passes --pre-release to vsce whenever it's still true; that fails outright since these VSIXs were packaged as stable (Cannot use '--pre-release' flag with a package that was not packaged as pre-release):

sh
gh release edit v<version> --prerelease=false --title "Release <version> - Tested & Approved" --latest --repo forcedotcom/salesforcedx-vscode

Also updates the release title from "Ready for Testing" to "Tested & Approved" to reflect that manual testing passed, and marks it --latest so GitHub (and anything resolving "the latest release" via the API) points at it instead of whatever shipped previously.

Flip auto-fires both workflows via on.release.types: [released] (publishVSCode.yml, publishOpenVSX.yml):

  • publish → vscode-publish-release-vsix.yml with release-tag = that tag (VSIXs on the GH release)
  • prepare-release-metadata checks out ref: develop only to compare tags + set Code Builder / GUS patch-vs-minor metadata — does not publish develop's tree
  • Open VSX checks out $RELEASE_TAG
Show full SKILL.md (252 more words)Show less

Both still need publish environment approval. Manual workflow_dispatch = retry only.

Dispatch both publishVSCode.yml and publishOpenVSX.yml — dispatching one does not trigger the other (verified against run history: manual dispatches always appear as two separate workflow_dispatch runs, never a cascade). Use the tag form (v<version>, e.g. v67.12.0):

sh
gh workflow run publishVSCode.yml  -f version="v<version>"      --repo forcedotcom/salesforcedx-vscode
gh workflow run publishOpenVSX.yml -f release-tag="v<version>" --repo forcedotcom/salesforcedx-vscode

Both gated by the publish environment — user will approve each run in GitHub UI (Actions → run → Review pending → Approve + deploy).

Tell user: "Triggered both publish workflows (Marketplace + Open VSX). You'll need to approve the environment gate on each in GitHub Actions UI."

Monitor runs:

sh
gh run list --workflow=publishVSCode.yml  -L 1 --json databaseId,status,url --repo forcedotcom/salesforcedx-vscode
gh run list --workflow=publishOpenVSX.yml -L 1 --json databaseId,status,url --repo forcedotcom/salesforcedx-vscode
gh run watch <databaseId> --repo forcedotcom/salesforcedx-vscode

Verify live:

Step 5 — Slack post

Compose from packages/salesforcedx-vscode/CHANGELOG.md (top section). Format:

  • Header: *Salesforce Extensions for VS Code v<version> is out* :tada:
  • Link: bare URL on its own line — VS Code Marketplace: https://marketplace.visualstudio.com/items?itemName=salesforce.salesforcedx-vscode (see Changelog tab for full details). Do not use Slack's <url|text> bracket-pipe syntax: anything outside Slack's own composer (chat clients, clipboards, other markdown renderers) tends to do naive URL auto-detection, grabs everything up to the next whitespace, and mangles the link — encoding the | as %7C and swallowing the leading text into the URL.
  • Sections: *Added* / *Fixed*
  • Subsections (#### foo) → blockquote (> foo)
  • Drop PR/issue trailers

Show composed post. If Slack MCP available → offer to post/draft to #platform-dev-tools. Wait for approval before sending.

Emergency Hotfixes

For critical security/production bugs, use the separate /patch-release skill.

See patch-release/SKILL.md for emergency patch release workflow.

Conventions

  • All gh commands use --repo forcedotcom/salesforcedx-vscode
  • Don't approve publishes until manual testing done
  • Patch releases bypass timeline for emergencies only
  • Always cherry-pick fixes to develop after publishing

© forcedotcom, BSD-3-Clause. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/release of forcedotcom/salesforcedx-vscode.

Open the folder on GitHubat commit f7bb6fe

Compare with similar skills

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.

Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release this skillforcedotcom/salesforcedx-vscode1k—~1.7kAutomated safety check: PassBSD-3-Clause
Release Roslynatordotnet/roslynator3.5k—~1kAutomated safety check: PassCustom licence
Releasesignageos/vscode-sops122—~2.2kAutomated safety check: NotesMIT
Releasequerylenshq/ef-querylens225—~887Automated safety check: PassMIT
Rocky Releaserocky-data/rocky304—~4.1kAutomated safety check: WarnApache-2.0
Vscode Release Notes Writerforyourhealth111-pixel/Vibe-Skills3.6k—~1.4kAutomated safety check: PassApache-2.0

Similar skills

  • Release Roslynator

    dotnet/roslynator

    Official

    A skill your agent uses when shipping a roslynator release, rolling CHANGELOG.md [Unreleased], updating the VS Code extension changelog, creating a GitHub v release, or optionally tagging cli-v.

    3.5k GitHub stars~1k tokensUpdated 3 days ago
    DevelopmentAuto-check passed

  • Release

    signageos/vscode-sops

    Releases the vscode-sops extension end-to-end: determines the next version from the bump history, updates CHANGELOG.md and package.json/package-lock.json, builds via vscode:prepublish, publishes to…

    122 GitHub stars~2.2k tokensUpdated 6 mo ago
    DevelopmentAuto-check: notes

  • Release

    querylenshq/ef-querylens

    A skill your agent uses when: creating a release, publishing a version, cutting a release, tagging a release, releasing plugin, release workflow, prepare release, create git tag, create GitHub…

    225 GitHub stars~887 tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Rocky Release

    rocky-data/rocky

    Tag-namespaced release workflow for the Rocky monorepo. An agent skill from rocky-data/rocky.

    304 GitHub stars~4.1k tokensUpdated today
    DevelopmentAuto-check: warnings

  • Vscode Release Notes Writer

    foryourhealth111-pixel/Vibe-Skills

    Guidelines for writing and reviewing Insiders and Stable release notes for Visual Studio Code.

    3.6k GitHub stars~1.4k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Setup Context A8c

    woocommerce/woocommerce-ios

    Set up the ContextA8C MCP server for accessing Automattic internal resources (Slack, Linear, P2s, GitHub Enterprise, etc.)

    358 GitHub stars~627 tokensUpdated today
    Agent WorkflowsAuto-check: notes

More from forcedotcom/salesforcedx-vscode

All 37 skills in this repo

  • Command UI

    forcedotcom/salesforcedx-vscode

    Command palette, CodeLens, context menus, package.nls titles, and NotificationModeService.

    1k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Services Extension Consumption

    forcedotcom/salesforcedx-vscode

    Consume the salesforcedx-vscode-services extension API. An agent skill from forcedotcom/salesforcedx-vscode.

    1k GitHub stars~5k tokensUpdated today
    Auto-check passed

  • Changelog

    forcedotcom/salesforcedx-vscode

    Polish the automated CHANGELOG on develop before the next stable build.

    1k GitHub stars~3.3k tokensUpdated today
    Auto-check passed

  • Core Extension API

    forcedotcom/salesforcedx-vscode

    Public API exported by salesforcedx-vscode-core activate(). An agent skill from forcedotcom/salesforcedx-vscode.

    1k GitHub stars~842 tokensUpdated today
    Auto-check passed

  • Drivable Vscode

    forcedotcom/salesforcedx-vscode

    Operate a real VS Code instance through drivable-vscode. An agent skill from forcedotcom/salesforcedx-vscode.

    1k GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Effect Best Practices

    forcedotcom/salesforcedx-vscode

    Enforces Effect-TS patterns for services, errors, layers, atoms, and Effect.pipe composition.

    1k GitHub stars~6.2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Release

What does Release do?

Run the VS Code extension release workflow end-to-end. An agent skill from forcedotcom/salesforcedx-vscode. Release is an agent skill from forcedotcom/salesforcedx-vscode. Run the VS Code extension release workflow end-to-end.

When should I use Release?

Release fits situations like: publishing a release; running prerelease; verifying the release branch; polishing changelog for release.

How do I install Release in Claude Code?

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

How do I install Release in Codex?

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

Can I use 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 forcedotcom/salesforcedx-vscode --skill 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/release, .gemini/skills/release, .github/skills/release and .opencode/skills/release in your project.

What does Release need to run?

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

Does Release access the network?

SKILL.md names 3 domains. In commands or code: marketplace.visualstudio.com; the agent is likely to contact it when it follows the instructions. As links in the text: salesforce.enterprise.slack.com and open-vsx.org. This is read from the text; nothing was executed.

Is 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 Release use?

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

How many tokens does Release use?

About 1.7k tokens (SKILL.md is roughly 6.7k 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 Release?

Skills that share tags, products or a category with Release: Release Roslynator (dotnet/roslynator, 3.5k stars), Release (signageos/vscode-sops, 122 stars), Release (querylenshq/ef-querylens, 225 stars) and Rocky Release (rocky-data/rocky, 304 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release?

forcedotcom (a GitHub organization) maintains it in forcedotcom/salesforcedx-vscode, which has 1,035 GitHub stars. The repository holds 37 skills in this directory. The repository was last updated on October 7, 2026.

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