Dx Org Switch

This handles switching your default Salesforce org through the CLI, which is one of those things you do constantly when juggling multiple sandboxes, scratch orgs, or prod environments. It sets target-org locally by default (project-scoped) or globally if you ask for it, and includes a verification step since the CLI's JSON output won't tell you which scope actually took effect. The instructions are thorough about when to use local versus global scope and include a helpful reminder that SF_TARGET_ORG environment variables will override everything. Solid for teams that context-switch between orgs throughout the day.

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

View on GitHub

Install

$ npx -y skills add forcedotcom/sf-skills --skill dx-org-switch --agent claude-code

Installs into .claude/skills of the current project.

Files

Steps

Identify the org: the user provides a username or alias (orgIdentifier). If not provided, run sf org list to show authenticated orgs and ask the user which one to use.
Set the default org:
- Local (default): sf config set target-org <orgIdentifier>
  - Applies only within the current project directory. Use this for normal project work.
- Global (only if user explicitly requests): sf config set target-org <orgIdentifier> --global
  - Applies system-wide across all directories. Use when working outside a project or when the user asks for global scope.
- If this fails, report the error and suggest running sf org login web if the org may not be authorized.
Verify:
- sf config get target-org --json
- Note: the JSON output does not include a scope/location field — it cannot confirm whether the value is local or global. Confirm the value only, e.g.: target-org is now set to: <value>
- If it fails, report the error and advise running sf config get target-org.