Commerce B2b Open Code Components Replace

This handles the tedious work of swapping out-of-the-box B2B Commerce components for their open source equivalents in your site metadata. It scans your content.json files, cross-references an authoritative mapping table, and lets you pick which components to replace via checkboxes. The workflow is careful: it delegates to another skill to ensure the open source repo is cloned and components are copied first, then does a dry run to show you exactly what can be replaced, what's missing from the repo, and what has no mapping. Saves you from manually hunting through JSON files and mistyping component names. Most useful when you're migrating a store to open code components and want to avoid the manual grep and replace dance.

skills.sh installs: 4.6K
GitHub stars: 1.2K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add forcedotcom/sf-skills --skill commerce-b2b-open-code-components-replace --agent claude-code

Installs into .claude/skills of the current project.

Files

Replacing OOTB B2B Commerce Components with Open Code

This skill replaces OOTB (out-of-the-box) B2B Commerce component definitions in site metadata content.json files with their open source site: equivalents, or looks up the equivalent open code component for given OOTB definitions without making changes. It uses an authoritative mapping loaded from assets/ootb-to-open-code-mapping.json.

Scope

Modes: Full replace runs the scan (Step 1), user selection if needed, then content.json updates (Step 2–3). Lookup only (user asks for equivalents but not to change files): apply the mapping-authority rule and report OOTB → site: for the named components or for definitions found in the scoped content.json — do not call Write unless the user confirms replacement. View-scoped work: limit file discovery and reads to sfdc_cms__view/<ViewName>/ (or the path the user gives) instead of all views.