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

Patch Release

by forcedotcom in forcedotcom/salesforcedx-vscode

Run emergency patch releases for critical hotfixes. An agent skill from forcedotcom/salesforcedx-vscode.

BSD-3-ClauseAuto-check passed

Install Patch Release

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

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

GitHub CLI
$ gh skill install forcedotcom/salesforcedx-vscode patch-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/patch-release .claude/skills/patch-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
patch-release
GitHub stars
1k
Token cost
~1.6k tokens
SKILL.md length
538 words
Files
1
Skills in repo
37
Repo updated
First seen
Licence
BSD-3-Clause

At a glance

Run emergency patch releases for critical hotfixes. An agent skill from forcedotcom/salesforcedx-vscode.

  • Works in 10 steps: Create release-base branch → Check out branch locally → Apply fixes → …
  • User explicitly requests patch release workflow
  • SKILL.md covers When to use, Steps, Multiple patches on same base and Emergency Pre-release Hotfix…, plus 2 more sections
  • Calls gh, git and node

What it does

Patch Release is an agent skill from forcedotcom/salesforcedx-vscode. Run emergency patch releases for critical hotfixes. Use when user explicitly requests patch release workflow.

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

The repository describes itself as: Salesforce Extensions for VS Code. The licence is BSD-3-Clause.

When your agent uses it

  • User explicitly requests patch release workflow

Example prompts

  • “/patch-release”

Workflow steps

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

  1. Create release-base branch
  2. Check out branch locally
  3. Apply fixes
  4. Build patch release
  5. Test VSIX files
  6. Publish to marketplace
  7. Cherry-pick fixes to develop
  8. Cleanup (after publishing)
  9. Build emergency pre-release VSIXs
  10. Publish to marketplace as pre-release

What it can do on your machine

Read from SKILL.md and the folder at commit 27807f6. 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
    • git
    • node

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

  • Network

    No URLs in SKILL.md. Its commands use gh 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

Patch Release loads about 1.6k tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 538 words of instructions outside code blocks.

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

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 27807f6, republished under its BSD-3-Clause licence (© forcedotcom). 538 words, ~1,629 tokens.

Download SKILL.mdSave it as .claude/skills/patch-release/SKILL.md (or your agent's skills folder).
name
patch-release
description
Run emergency patch releases for critical hotfixes. Use when user explicitly requests patch release workflow.
review
never

Patch Release Skill

User-invocable only. Run emergency patch releases for critical hotfixes.

Invoke: /patch-release or user explicitly requests patch release workflow.

DO NOT use during /release — this skill is for emergency hotfixes only.

When to use

  • Security vulnerabilities requiring immediate fix
  • Critical production bugs affecting customers
  • Showstopper issues that cannot wait for next stable release

Steps

1. Create release-base branch
sh
gh workflow run create-patch-release-branch.yml -f baseVersion="67.12.0" --repo forcedotcom/salesforcedx-vscode

Creates release-base/v67.12.x from stable tag; copies latest version helpers from develop.

2. Check out branch locally
sh
git fetch origin
git checkout release-base/v67.12.x
3. Apply fixes

Make code changes, commit with conventional messages (fix:, feat:, etc.), push to branch:

sh
git commit -m "fix: <message>"
git push origin release-base/v67.12.x
4. Build patch release
sh
gh workflow run build-and-release-patch-branch.yml -f releaseBranch="release-base/v67.12.x" --repo forcedotcom/salesforcedx-vscode

Auto-calculates patch version (v67.12.0 → v67.12.1), tags exact commit from branch HEAD, builds VSIXs.

5. Test VSIX files

Download and install locally for testing:

sh
gh release download v67.12.1 --dir ~/Downloads/v67.12.1 --pattern '*.vsix' --repo forcedotcom/salesforcedx-vscode
find ~/Downloads/v67.12.1 -type f -name "*.vsix" -exec code --install-extension {} \;

Run manual QA tests. See docs/release-testing-guide.md for testing checklist.

6. Publish to marketplace

If tests pass, dispatch both workflows for full coverage (VS Code Marketplace + Open VSX) — dispatching one does not trigger the other, there is no cascade between them. Set isHotfix=true on each so its own gate-check tests the exact patch commit directly (this build never went through develop's branch protection or any nightly pipeline):

sh
gh workflow run publishVSCode.yml -f version="v67.12.1" -f isHotfix=true --repo forcedotcom/salesforcedx-vscode
gh workflow run publishOpenVSX.yml -f release-tag="v67.12.1" -f isHotfix=true --repo forcedotcom/salesforcedx-vscode
7. Cherry-pick fixes to develop

Merge functional fixes back to develop (NOT version bumps):

sh
git checkout develop && git pull origin develop
git cherry-pick <commit-sha>  # functional fixes only, NOT "chore: bump versions"
git push origin develop

See docs/release-testing-guide.md for detailed cherry-pick workflow.

8. Cleanup (after publishing)

Delete the release-base branch:

sh
git push origin --delete release-base/v67.12.x

Multiple patches on same base

Reuse the same release-base/v67.12.x branch for multiple patches:

  1. Make additional fixes on the branch
  2. Run build-and-release-patch-branch.yml again (auto-increments to v67.12.2, v67.12.3, etc.)
  3. Test and publish each patch
  4. Cherry-pick all functional fixes to develop
  5. Delete branch after final patch

Emergency Pre-release Hotfix (Marketplace in ~5 min)

For immediate marketplace hotfix as pre-release (bypasses stable testing):

The hotfix commit itself must bump package.json versions. build-github-release.yml never bumps versions in pre-release mode — it packages and tags whatever's already on the source ref as-is. The calculated/provided releaseVersion only names the git tag and release title; it has no effect on the version actually baked into the VSIX. If the source ref's package.json still has an old version, that's what gets published — potentially a version lower than what's already live, which registries will silently ignore as "latest." Bump the version as part of the hotfix commit itself (node scripts/update-release-versions.js <version>), same as any other release-affecting change to package.json.

Show full SKILL.md (162 more words)Show less
Step 1: Build emergency pre-release VSIXs
sh
# From hotfix branch
gh workflow run build-github-release.yml \
  -f emergencyPrerelease=true \
  -f startFromRef="hotfix/security-fix" \
  --repo forcedotcom/salesforcedx-vscode

# From specific commit
gh workflow run build-github-release.yml \
  -f emergencyPrerelease=true \
  -f startFromRef="abc123def456" \
  --repo forcedotcom/salesforcedx-vscode

Creates GitHub pre-release with VSIXs. Auto-calculates the git tag/release title as max(Marketplace, Open VSX) + 1 patch, or supply -f releaseVersion=X.Y.Z to override — this only names the tag, it does not change what's inside the VSIX (see version-bump note above).

Validation: Unit tests (compile + test) run at the authoritative gate: promote-to-prerelease.yml tests exact hotfix commit being promoted when isHotfix=true. E2E & full PR review skipped; ensure ref carefully reviewed before use.

Step 2: Publish to marketplace as pre-release
sh
gh workflow run promote-to-prerelease.yml \
  -f releaseTag="v67.13.7-nightly.develop.20260820" \
  -f isHotfix=true \
  --repo forcedotcom/salesforcedx-vscode

Publishes VSIXs to marketplace (Microsoft + Open VSX) as pre-release.

Timeline: ~3 min build + ~2 min promote = ~5 min total to marketplace.

Alternative: Formal Version from Arbitrary Ref

For time-critical fixes requiring proper version tracking (not nightly format):

sh
# Build from hotfix branch with version bump
gh workflow run build-github-release.yml \
  -f startFromRef="hotfix/security-fix" \
  -f releaseVersion="67.12.1" \
  --repo forcedotcom/salesforcedx-vscode

# Build from specific commit with version bump
gh workflow run build-github-release.yml \
  -f startFromRef="abc123def456" \
  -f releaseVersion="67.12.1" \
  --repo forcedotcom/salesforcedx-vscode

Creates isolated release-staging/v67.12.1 branch with version bump. publishVSCode.yml and publishOpenVSX.yml test the commit (compile + test, isHotfix=true) before publishing. E2E tests and full PR review are skipped. Test VSIXs and publish as stable release.

References

© 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/patch-release of forcedotcom/salesforcedx-vscode.

Open the folder on GitHubat commit 27807f6

Compare with similar skills

Patch 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.

Patch Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Patch Release this skillforcedotcom/salesforcedx-vscode1k—~1.6kAutomated safety check: PassBSD-3-Clause
Patch Release CheckClickHouse/ClickHouse50k—~4kAutomated safety check: NotesApache-2.0
Emergency Hotfix WorkflowDonchitos/Claude-Code-Game-Studios26k—~2.9kAutomated safety check: NotesMIT
Releasepaperclipai/paperclip99k—~2.4kAutomated safety check: PassMIT
Release Generate Release Notesmountain-loop/yaak19k—~548Automated safety check: PassMIT
Verify Releaseopenclaw/openclaw392k—~2.4kAutomated safety check: PassMIT

Similar skills

  • Patch Release Check

    ClickHouse/ClickHouse

    Check whether ClickHouse's supported versions (last 3 majors + latest LTS) have recent stable patch releases, diagnose why the scheduled AutoReleases pipeline failed, and identify which releases…

    50k GitHub stars~4k tokensUpdated today
    DatabasesAuto-check: notes

  • Emergency Hotfix Workflow

    Donchitos/Claude-Code-Game-Studios

    Runs an emergency fix process for severe bugs: a severity check, a written hotfix record, and a branch cut from the shipped release rather than main.

    26k GitHub stars~2.9k tokensUpdated 8 days ago
    DevelopmentAuto-check: notes

  • Release

    paperclipai/paperclip

    Coordinate a full Paperclip release across engineering verification, npm, GitHub, smoke testing, and announcement follow-up.

    99k GitHub stars~2.4k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Release Generate Release Notes

    mountain-loop/yaak

    Generate Yaak release notes from git history and PR metadata, including feedback links and full changelog compare links.

    19k GitHub stars~548 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Verify Release

    openclaw/openclaw

    Verify regular or extended-stable OpenClaw releases against the exact publication surfaces, workflow identities, package provenance, smoke tests, and live Gateway behavior expected for that release…

    392k GitHub stars~2.4k tokensUpdated today
    Testing & QAAuto-check passed

  • Release

    codewhale-hq/Codewhale

    Prepare a named version: preflight, version consistency, build/package, smoke test, checksums/notes, and release readiness.

    41k GitHub stars~189 tokensUpdated today
    Testing & QAAuto-check passed

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

Questions about Patch Release

What does Patch Release do?

Run emergency patch releases for critical hotfixes. An agent skill from forcedotcom/salesforcedx-vscode. Patch Release is an agent skill from forcedotcom/salesforcedx-vscode. Run emergency patch releases for critical hotfixes.

When should I use Patch Release?

Patch Release fits situations like: user explicitly requests patch release workflow.

How do I install Patch Release in Claude Code?

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

How do I install Patch Release in Codex?

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

Can I use Patch 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 patch-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/patch-release, .gemini/skills/patch-release, .github/skills/patch-release and .opencode/skills/patch-release in your project.

What does Patch Release need to run?

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

Does Patch Release access the network?

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

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

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

About 1.6k tokens (SKILL.md is roughly 6.5k 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 Patch Release?

Skills that share tags, products or a category with Patch Release: Patch Release Check (ClickHouse/ClickHouse, 50k stars), Emergency Hotfix Workflow (Donchitos/Claude-Code-Game-Studios, 26k stars), Release (paperclipai/paperclip, 99k stars) and Release Generate Release Notes (mountain-loop/yaak, 19k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Patch 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 8, 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.