Agent skill · software engineering · jeremylongshore
salesforce-ci-integration
Build fork-safe Salesforce CI with secretless static and fixture gates, protected non-production validation, and separately approved production promotion. Use when automating delivery. Trigger with "add Salesforce CI".
Why this skill is useful
Adds a complete CI/CD pipeline setup for Salesforce with executable scripts and specific commands that aren't commonly known.
What it needs
Requires node, npm, openssl installed locally. Requires github, salesforce account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Fork-Safe Salesforce Continuous Integration Overview Separate deterministic untrusted-code checks from credentialed org validation so pull requests cannot access Salesforce secrets or mutate a customer org. Prerequisites Repository, Salesforce DX project, package layout, branch policy, and immutable dependency lock Synthetic metadata and API fixtures plus an authorized validation org CI, Salesforce admin, security, release, and code owners with environment protection rules 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 CLI can validate and deploy source against authorized orgs, but exact commands, test levels, authentication, and metadata behavior vary with the pinned CLI and project. Fork pull requests must be treated as untrusted. Authentication Keep org authorization, certificates, secrets, and aliases out of fork-origin jobs, logs, caches, and artifacts. Resolve protected credentials only after trusted code, environment approval, and exact-head verification. Instructions 1. Pin runtime, package manager, Salesforce CLI, plugins, lockfiles, action SHAs, and generated-artifact checks. 2. Create a secretless lane for formatting, linting, static analysis, unit tests, schema tests, fixture contracts, and source validation. 3. Model auth expiry, permission denial, API-version drift, metadata conflict, partial deployment, limits, and rollback in fixtures. 4. Restrict credentialed jobs to protected branches or environments with no fork secrets, minimal permissions, concurrency, and timeouts. 5. Against an approved non-production org, verify identity, validate the bounded deployment, run required tests, and capture IDs. 6. Require human approval and immutable artifact promotion before any production validation or deployment job. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesforce-ci-integration