agentleFS
Sign inStart free
forcedotcomforcedotcom/salesforcedx-vscode/.claude/skills/patch-release/SKILL.md

patch-release

Skill1k starsChanged 25 days agoBSD-3-ClauseView on GitHub

Run emergency patch releases for critical hotfixes. Use when user explicitly requests patch release workflow.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about forcedotcom/salesforcedx-vscode

The biggest 5 of 52 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 52

Talked about on GitHub and Stack Overflow (52 times).

On GitHub · 50

45 more on GitHub

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read before proposing or running mutating commands.

    line 12
  2. Distinctive:

    Follow the matching canonical branch:

    line 21
  3. Distinctive:

    Follow the channel-specific publication procedure:

    line 34
  4. Very specific:

    After QA, first mark the stable-packaged release isPrerelease=false.

    line 36
  5. Very specific:

    Leave automatic release-event runs unapproved (they skip hotfix tests).

    line 37
  6. Very specific:

    Verify live versions/channels in both registries.

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Patch Release

Emergency hotfixes only; not the weekly /release ceremony.

Canonical procedure: Patch Release Workflow. Read before proposing or running mutating commands. It covers stable patches, emergency prereleases, and later stable candidates from patched sources.

Required Decisions

  1. Inspect both registries, GitHub releases/tags, and pending publication runs.
  2. Show exact released source tags/SHAs, reviewed fix commits, unused target versions, changelog scope, and commands. Get explicit confirmation before builds, publication, cancellation, or approval.
  3. Follow the matching canonical branch:
    • Stable patch: exact stable release tag, not its original nightly; releaseBranch input.
    • Emergency prerelease: exact published prerelease source; commit package/lockfile version changes using node scripts/update-release-versions.js <version> before building. Emergency releaseVersion names the tag only, not the VSIX version.
    • Later stable candidate: separate decision/build; explicit patched startFromRef, unused releaseVersion, complete original release changes plus fix in changelog. Hotfix promotion does not make stable auto-detection select that source.
  4. Install/test each checkout; QA the exact new artifacts in the affected runtime. Record evidence; never infer passing tests.
  5. Follow the channel-specific publication procedure:
    • Stable: current hotfix workaround. After QA, first mark the stable-packaged release isPrerelease=false. Leave automatic release-event runs unapproved (they skip hotfix tests); cancel only after confirmation. Dispatch both publishers from develop with isHotfix=true; approve only those runs and require both gates to pass.
    • Prerelease: promote the exact hotfix tag with isHotfix=true; promotion tests the source commit and publishes both registries. Keep it prerelease; Tested & Approved applies only to stable-packaged candidates.
  6. Verify live versions/channels in both registries. Merge functional fixes to develop separately through a PR; exclude release-only version/tooling commits.

Existing candidates count as used versions, even if never published. Recovery uses a new version, never deleting/recreating releases, retagging, or replacing assets. An existing candidate's pending publications need a separate decision; 2 immediate channel hotfixes do not authorize a third candidate build.

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.

Check your setup, free