Skill

b2c-code

Deploys cartridges, manages code versions on Salesforce B2C Commerce instances/sandboxes using b2c CLI. Use for uploading code, activating versions, watching file changes during development.

Bash

Node

deployment

devops

npx claudepluginhub salesforcecommercecloud/b2c-developer-tooling --plugin b2c-cli

Tool Access

This skill uses the workspace's default tool permissions.

Preview

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

Supporting Assets

evals/trigger-evals.json

SKILL.md

Similar Skills

skill-lookup

159.9k

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

prompt-lookup

159.9k

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

next-compile

139.2k

Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.

1 file

vercel-next-js-2

Stats

Parent Repo Stars34

Parent Repo Forks10

Last CommitMar 29, 2026

Actions

View Source View Plugin View on GitHub View README

B2C Code Skill

Use the b2c CLI to deploy 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).

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

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

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: Activating a code version triggers Custom API endpoint registration. If you've added or modified Custom APIs, use --reload with deploy or activate to register them. Check registration status with the b2c-cli:b2c-scapi-custom skill.

Delete Code Version

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

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