salesforce-multi-org-promotion

Orchestrates Salesforce metadata promotion across Dev, QA, UAT, and Prod orgs with drift detection.

1|Updated May 7, 2026
One-click install
npx skills add https://github.com/amanpraaj/sf-skill-hub --skill salesforce-multi-org-promotion-amanpraaj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: salesforce-multi-org-promotion
Source: https://github.com/amanpraaj/sf-skill-hub/tree/main/skills/salesforce/salesforce-multi-org-promotion
Command: npx skills add https://github.com/amanpraaj/sf-skill-hub --skill salesforce-multi-org-promotion-amanpraaj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Promoting Salesforce changes across multiple orgs often leads to environment drift, broken dependencies, and inconsistent deployments. This Skill provides a structured promotion workflow that detects metadata drift, sequences deployments in dependency-safe order, and validates each environment hop before proceeding. ## Core Features & Use Cases - Org Topology Mapping: Builds a map of your Dev, Integration, QA, UAT, Pre-Prod, and Prod environments to plan promotion paths. - Drift Detection: Compares target org metadata against expected baselines and blocks promotion on critical unmanaged drift. - Gated Promotion Sequencing: Promotes changes hop-by-hop with validation gates and maintains a promotion ledger of deployment IDs for auditability. - Use Case: An enterprise release manager needs to push a new Apex feature from Dev through QA and UAT into Prod. The Skill detects drift in UAT, blocks the promotion until resolved, then validates each hop and records deployment IDs. ## Quick Start Ask the agent to plan and execute a promotion of your current Salesforce changes from Dev through QA and UAT to Prod with drift checks at each hop.

Frequently Asked Questions about salesforce-multi-org-promotion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I promote Salesforce changes across multiple orgs?▼

Build an org topology map, detect metadata drift against baselines, then promote in dependency-safe order from Dev through Integration, QA, UAT, and Pre-Prod to Prod. Validate each hop before the next promotion and record deployment IDs in a ledger.

How to detect metadata drift between Salesforce environments?▼

Compare the target org's metadata against the expected baseline before each promotion. The workflow blocks promotion when critical unmanaged drift is found, preventing inconsistent deployments from reaching downstream environments.

What is the correct Salesforce promotion sequence for enterprise pipelines?▼

The recommended sequence is Dev to Integration to QA to UAT to Pre-Prod to Prod. Each hop requires a gate pass, meaning validation must succeed before changes advance to the next environment.

Can this handle deployments that fail partway through a pipeline?▼

Yes, the per-hop validation gate stops the promotion when a deployment fails validation, so later environments are never touched. The promotion ledger of deployment IDs lets you audit exactly which hops completed.

When is multi-org promotion orchestration not needed?▼

Single-org development or simple two-environment setups with a basic change set or single sfdx deployment do not need full topology mapping and drift gating. This workflow targets enterprise pipelines with three or more environments.