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'.
What this skill does
# 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`). ## Examples ### Deploy Cartridges ```bash # 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 ``` ### Download Cartridges ```bash # 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 ```bash # 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 ```bash # list code versions on the instance b2c code list # list with JSON output b2c code list --json ``` ### Activate Code Version ```bash # 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 ```bash # 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
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.