forcedotcom/sf-skills

dx-org-switch

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

Ver código fuente

Cómo usar

  1. Copia el comando y revisa el paquete antes de instalarlo en tu entorno de agente.
  2. Consulta las herramientas, credenciales y entornos necesarios en el documento original.
  3. Describe las entradas y el resultado deseado; contrasta la salida con las fuentes.
npx skills add https://github.com/forcedotcom/sf-skills --skill dx-org-switch

Antes de empezar

  • La instalación no incluye suscripción al modelo, cuota API ni permisos sobre tus archivos.
  • Las estrellas e instalaciones reflejan actividad, no una prueba independiente de calidad o seguridad.
Documento original del Skill

Contenido del repositorio de origen con títulos, ejemplos, código, tablas, enlaces e imágenes preservados.

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

Relacionados por tarea

del mismo repositorio

Más Skills

Todos los Skills
forcedotcom
Comunidad

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.

instalaciones
1
GitHub Stars
1,1 mil
Actualizado
23 oct
forcedotcom
Comunidad

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

instalaciones
1
GitHub Stars
1,1 mil
Actualizado
23 oct
forcedotcom
Comunidad

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

instalaciones
1
GitHub Stars
1,1 mil
Actualizado
23 oct
forcedotcom
Comunidad

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.

instalaciones
1
GitHub Stars
1,1 mil
Actualizado
23 oct