architect-cross-org-compare

Compare Salesforce org metadata to identify drifts, changes, and field mappings.

2|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/PranavNagrecha/Salesforce-Intelligence --skill architect-cross-org-compare
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect-cross-org-compare
Source: https://github.com/PranavNagrecha/Salesforce-Intelligence/tree/main/.claude/skills/architect-cross-org-compare
Command: npx skills add https://github.com/PranavNagrecha/Salesforce-Intelligence --skill architect-cross-org-compare

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires sfi compare, sfi field mapping, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill allows Salesforce architects to easily compare metadata between different Salesforce org environments, such as sandbox vs production, to identify drifts, changes, and discrepancies.

Core Features & Use Cases

  • Cross-Env Comparison: Compare metadata across different Salesforce orgs (sandbox vs production, prod vs prod).
  • Diff Detection: Identify and highlight changes between metadata snapshots of orgs.
  • Field Mapping: Determine how fields in one org map to fields in another org.
  • Use Case: For instance, a Salesforce architect might use this Skill to check for changes between the sandbox and production environments before deploying code, or to verify that user permissions are consistent across different orgs.

Quick Start

To compare the metadata of 'acme-prod' and 'acme-sandbox', use the command: compare-orgs acme-prod acme-sandbox.

Frequently Asked Questions about architect-cross-org-compare

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

FAQPage Schema
How do I compare Salesforce metadata between sandbox and production orgs?

Yes, this Skill compares metadata across different Salesforce environments, including sandbox versus production and production versus production. It highlights changes and discrepancies between metadata snapshots to help architects verify environment consistency.

What is field mapping in Salesforce and how does it work during an org comparison?

To compare Salesforce metadata between environments, use the `compare-orgs` command followed by the names of the target orgs, such as `compare-orgs acme-prod acme-sandbox`. This initiates the diff detection process to identify drifts and changes between the two environments.

Do I need specific tools to detect metadata drift across Salesforce environments?

To compare Salesforce metadata between environments, use the `compare-orgs` command followed by the names of the target orgs, such as `compare-orgs acme-prod acme-sandbox`. This initiates the diff detection process to identify drifts and changes between the two environments.

How do I check for metadata drift between Salesforce environments?

Yes, this Skill compares metadata across different Salesforce environments, including sandbox versus production and production versus production. It highlights changes and discrepancies between metadata snapshots to help architects verify environment consistency.

Can I verify user permissions are consistent across different Salesforce orgs?

Yes, you can verify user permission consistency across different Salesforce orgs by comparing their metadata. By identifying drifts and changes between environments, the comparison ensures configuration discrepancies are caught before deployment.