Agent skill · software engineering · jeremylongshore
salesforce-upgrade-migration
Migrate Salesforce API, seasonal release, CLI, client-library, metadata, and integration contracts under compatibility and rollback controls. Use when planning platform upgrades. Trigger with "plan a Salesforce upgrade".
Why this skill is useful
Provides specific migration scripts and version handling patterns for Salesforce and jsforce that the AI wouldn't reliably generate on its own.
What it needs
Requires git, jsforce installed locally. Requires salesforce account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Salesforce API and Toolchain Upgrade Control Overview Replace fixed-version guesswork with a complete inventory, compatibility matrix, staged validation, explicit ownership, and reversible consumer migration. Prerequisites Repository and org inventory with API versions, libraries, CLI, metadata, events, packages, and consumers Current Salesforce API EOL policy, seasonal release notes, dependency releases, and customer support constraints Test environments, representative fixtures, compatibility owner, migration window, and rollback point Tool Discipline Use Read, Glob, and Grep to inspect approved repository and evidence files, WebFetch to re-check current first-party Salesforce documentation, and Write or Edit only for secretless plans, fixtures, configuration, and redacted receipts. Current Contract Salesforce supports REST API versions for a documented lifecycle and retires older versions after notice. As of this review, versions 21.0 through 30.0 are unavailable, while the current support table must be re-fetched before every migration. Authentication Use existing approved app and principal contracts for compatibility tests. Do not add a password fallback, copy production tokens into test, or broaden access to compensate for an upgrade defect. Instructions 1. Inventory every explicit and library-default API version, CLI and library version, endpoint, schema snapshot, event client, and metadata consumer. 2. Re-fetch the API EOL table, release notes, client-library releases, CLI contract, and org upgrade schedule. 3. Classify each dependency as supported, deprecated, retired, preview, beta, or customer-specific and name an owner. 4. Build fixtures for response, error, pagination, metadata, event schema, limits, and partial-failure compatibility. 5. Upgrade one boundary at a time in a branch and validate static, unit, contract, sandbox, and deployment checks. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesforce-upgrade-migration--ccd26b