forcedotcom/sf-skills

dx-org-switch

Switches the active Salesforce org (default target-org) using the Salesforce CLI.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/forcedotcom/sf-skills --skill dx-org-switch

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Steps

  1. 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.
  2. 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.
  1. 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.

Notes

  • Unified CLI uses keys like target-org and target-dev-hub. Legacy sfdx keys (defaultusername, defaultdevhubusername) are deprecated in this context.
  • The sf CLI does not have --local or --scope flags for config set. Local scope is the default behavior.
  • If the org does not change after setting the config, check whether SF_TARGET_ORG is set — environment variables override config values.
  • Salesforce CLI config (unified) reference: https://developer.salesforce.com/docs/atlas.en-us.sfdxclireference.meta/sfdxclireference/clireferenceconfigcommandsunified.htm#clireferenceconfigsetunified

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
forcedotcom
コミュニティ

platform-custom-application-generate

Use this skill when users need to create or configure tab-based Salesforce Custom Applications with navigation, branding, and action overrides. Trigger when users mention custom apps, application metadata, app navigation, or organizing tabs into applications. Use when users want to create app containers for tabs and pages. Do NOT use when the goal is hosting a React UI bundle in the App Launcher — use experience-ui-bundle-custom-app-generate for that case.

導入数
1
GitHub Stars
1112
更新日
10月23日
forcedotcom
コミュニティ

platform-custom-field-generate

Use when users create, generate, or validate Salesforce Custom Field metadata. Trigger on custom fields, field types, Roll-Up Summary, Master-Detail/Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from a field, or scoping picklist values per record type; also field deployment errors, including a record type that won't deploy without a business process. DO NOT TRIGGER for creating/customizing the value set itself — a new GlobalValueSet o

導入数
1
GitHub Stars
1112
更新日
10月23日
forcedotcom
コミュニティ

platform-custom-metadata-type-generate

Use to create, generate, or validate Salesforce Custom Metadata Type metadata — the mdt object, fields, and deployable records. Trigger on custom metadata types, CMDT, mdt objects, .md-meta.xml files, or cross-org reference/config data; also admin-maintained mapping/lookup/crosswalk tables (config that changes without a deploy belongs in a CMDT, never hardcoded in Apex/Flow), and CMDT deploy errors. DO NOT TRIGGER for Custom Settings (use platform-custom-setting-generate), business-record object

導入数
1
GitHub Stars
1112
更新日
10月23日
forcedotcom
コミュニティ

platform-custom-report-type-generate

Use to create, generate, or validate Salesforce Custom Report Type metadata. Trigger on custom report types, CRTs, cross-object reports, report builder data sources, exposing fields for reporting across related objects, inner vs outer joins in reports, report type categories, or deployment errors for .reportType-meta.xml files. Do NOT trigger for running, editing, or filtering existing reports; creating report folders, dashboards, or list views; or non-authoring reporting questions.

導入数
1
GitHub Stars
1112
更新日
10月23日