skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
salesforcecommercecloud/b2c-developer-tooling82 installs

b2c-code

Deploy, download, and manage cartridge code versions on B2C Commerce instances. Use this skill whenever the user needs to upload or download cartridges to/from a sandbox, activate or delete code versions, watch for local file changes during development, or deploy a subset of cartridges. Also use when pushing code to an instance, pulling code from an instance, or setting up a dev workflow with live reload -- even if they just say 'push my code to the sandbox', 'download the code', or 'how do I activate the new version'.

How do I install this agent skill?

npx skills add https://github.com/salesforcecommercecloud/b2c-developer-tooling --skill b2c-code
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill provides instructions for managing Salesforce B2C Commerce code using the official CLI. It follows standard security practices for credential management and uses trusted resources from the Salesforce organization.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

  • Runlayerwarn

    1/1 file flagged

What does this agent skill do?

B2C Code Skill

Use the b2c CLI to deploy, download, and manage code versions on Salesforce B2C Commerce instances.

Tip: If b2c is not installed globally, use npx @salesforce/b2c-cli instead (e.g., npx @salesforce/b2c-cli code deploy).

MCP equivalent

Prefer cartridge_deploy for cartridge upload. Set codeVersion explicitly when needed; files selects up to 100 local files (64 MiB total), relative to projectDirectory, within discovered cartridges. Omit files for whole cartridges. Matching remote files are overwritten; selected-file mode preserves other files. reload may activate the target; keep upload success/warnings if reload fails. Code mode builtin/code-version-inspect reads active/rollback and activation metadata; builtin/site-cartridge-inspect reads site cartridge order and checks expected names. SCAPI dx/scripts/v1 provides version management; site/sites/v1 manages site paths. Use the CLI for watches, recursive downloads, and extra deployment flags.

Configuration & Authentication

The CLI auto-discovers the target instance and credentials from SFCC_* environment variables (including project .env), the selected project-local or shared dw.json, and configuration plugins. package.json supplies only non-sensitive defaults. Flags like --server, --client-id, --client-secret, --username, and --password are usually unnecessary — only pass them to override what's auto-detected.

With only a server configured, the first command opens a browser for the user to sign in with their Account Manager account and waits until they do; tell the user to finish signing in. Their Business Manager roles decide access, and a 403 names the missing permission (for example WebDAV_Manage_Customization for Cartridges). Code goes to the active code version; activating one (code activate, --activate, --reload) needs an API client.

Staging code upload needs a client certificate. Staging instances normally require two-factor (mTLS) code upload, so a deploy without a certificate fails, usually with 403 Forbidden on writes under Cartridges. Set certificate and certificate-passphrase (SFCC_CERTIFICATE, SFCC_CERTIFICATE_PASSPHRASE). Legacy realms use a certificate signed by a CA bundle from Salesforce Support and the cert.staging.* WebDAV hostname. Hyperforce realms use a CA the user registers through eCDN (b2c-cli:b2c-ecdn, b2c ecdn mtls). See Two-Factor Authentication.

Reload needs a second code version. --reload toggles activation through another code version. If the instance has only one, create an empty one first (b2c webdav mkdir --root cartridges version2).

Run b2c setup inspect to see the resolved configuration and which source provided each value (use --json for scripting; secrets stay masked by default). For precedence rules and troubleshooting, see the b2c-cli:b2c-config skill.

Examples

Deploy Cartridges

# deploy all cartridges from current directory
b2c code deploy

# deploy cartridges from a specific directory
b2c code deploy ./my-cartridges

# deploy to a specific server and code version
b2c code deploy --server my-sandbox.demandware.net --code-version v1

# deploy and reload (re-activate) the code version
b2c code deploy --reload

# delete existing cartridges before upload and reload
b2c code deploy --delete --reload

# deploy only specific cartridges
b2c code deploy -c app_storefront_base -c plugin_applepay

# deploy every discovered cartridge, ignoring a `cartridges` list in dw.json or SFCC_CARTRIDGES
b2c code deploy --all

# exclude specific cartridges from deployment
b2c code deploy -x test_cartridge

# replace the directory names skipped inside cartridges (default: node_modules,.git,coverage,.cache,tmp,temp)
b2c code deploy --cartridge-ignore-dirs node_modules,.git,build

# large code versions are split into archives of up to 200 MiB automatically;
# lower the limit if uploads are rejected (413) or keep dropping
b2c code deploy --max-archive-size 100mb

Download Cartridges

# download all cartridges from the active code version
b2c code download

# download to a specific directory
b2c code download -o ./downloaded

# download from a specific server and code version
b2c code download --server my-sandbox.demandware.net --code-version v1

# download only specific cartridges
b2c code download -c app_storefront_base -c plugin_applepay

# exclude specific cartridges from download
b2c code download -x test_cartridge

# mirror: extract to local cartridge project locations
b2c code download --mirror

Watch for Changes

# watch cartridges and upload changes automatically
b2c code watch

# watch a specific directory
b2c code watch ./my-cartridges

# watch with specific server and code version
b2c code watch --server my-sandbox.demandware.net --code-version v1

# watch only specific cartridges
b2c code watch -c app_storefront_base

# watch excluding specific cartridges
b2c code watch -x test_cartridge

List Code Versions

# list code versions on the instance
b2c code list

# list with JSON output
b2c code list --json

Activate Code Version

# activate a code version
b2c code activate <version-name>

# reload (re-activate) the current code version
b2c code activate --reload

Note: Activation is idempotent. If the version is already active, the command succeeds without making a change. If you've uploaded code or changed Custom APIs in the active version, use --reload with deploy or activate to force a refresh and register the endpoints. Check registration status with the b2c-cli:b2c-scapi-custom skill.

Delete Code Version

# delete a code version
b2c code delete <version-name>

API Backend

code list, code activate, code delete, and the active-version discovery / activate / reload steps in code deploy run over SCAPI. Configure shortCode, tenantId, and the sfcc.scripts / sfcc.scripts.rw scopes and they work out of the box. Read scope (sfcc.scripts) covers code list / discovery; write scope (sfcc.scripts.rw) covers activate, delete, reload, and the --activate / --reload flags on deploy.

code deploy (file upload itself), code download, and code watch always use WebDAV — only the surrounding code-version operations use SCAPI.

OCAPI is deprecated and disabled on newer instances. --api-backend auto (the default) falls back to the OCAPI Data API on safe SCAPI capability/auth/request rejections; force a backend with --api-backend scapi|ocapi if needed. The --reload flag forces a code cache reload as activate(alternate) + activate(target), using whichever backend the command selected — so it works on OCAPI-disabled instances when SCAPI is configured.

More Commands

See b2c code --help for a full list of available commands and options in the code topic.

Note: b2c code deploy uploads cartridge code to an instance. To manage which cartridges are active on a site (the cartridge path), see the b2c-cli:b2c-sites skill for the b2c sites cartridges commands.

Related Skills

  • b2c-cli:b2c-sites - Manage site cartridge paths (list, add, remove, set active cartridges)
  • b2c-cli:b2c-scapi-custom - Check Custom API registration status after deployment
  • b2c-cli:b2c-webdav - Low-level file operations (delete cartridges, list files)
  • b2c:b2c-custom-api-development - Creating Custom API endpoints

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/salesforcecommercecloud/b2c-developer-tooling/b2c-code">View b2c-code on skillZs</a>