sf-deploy

Automate Salesforce deployments with sf v2 using manifest-based workflows.

6|Updated Dec 20, 2023
One-click install
npx skills add https://github.com/ronitnuguru/Package-Visualizer --skill sf-deploy-ronitnuguru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sf-deploy
Source: https://github.com/ronitnuguru/Package-Visualizer/tree/main/.cursor/skills/sf-deploy
Command: npx skills add https://github.com/ronitnuguru/Package-Visualizer --skill sf-deploy-ronitnuguru

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Salesforce deployments are complex and error-prone, requiring careful coordination of metadata, tests, and environment setup across multiple tools and orgs.

Core Features & Use Cases

  • Enforces an end-to-end deployment workflow by orchestrating metadata types in the recommended order (Objects/Fields → Permissions → Apex → Flows) and handling activation.
  • Supports dry-run validation, manifest-based deployment, and CI/CD-friendly workflows to enable repeatable releases across multiple orgs.
  • Integrates with cross-skill tools (sf-metadata, sf-flow, sf-data, agent deployment) to enable end-to-end release orchestration.

Quick Start

Validate a deployment with a dry-run and then execute the full deployment to a target org when ready.

Frequently Asked Questions about sf-deploy

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

FAQPage Schema
How do I automate Salesforce deployments using sf v2?

Salesforce deployments are automated using sf v2 by orchestrating metadata, Apex, and Flows in a recommended sequence. This workflow supports scratch orgs, 2GP upgrades, and CI/CD pipelines, coordinating environment setup and testing to reduce manual errors.

What is the recommended deployment sequence for Salesforce metadata?

The recommended deployment sequence for Salesforce metadata is Objects and Fields, followed by Permissions, then Apex, and finally Flows. This staged deployment order ensures dependencies are resolved correctly before activating downstream components.

Can I validate Salesforce metadata changes with a dry-run before executing a full deployment?

Yes, you can validate Salesforce metadata changes with a dry-run before executing a full deployment. This allows you to test deployment validity against a target org and handle manifest-based workflows without committing changes.

Does this Salesforce deployment workflow support CI/CD pipelines and scratch orgs?

Yes, this Salesforce deployment workflow supports CI/CD pipelines and scratch orgs. It applies manifest-based deployment and staged release scenarios to enable repeatable releases across multiple orgs, including 2GP upgrade environments.

How do I orchestrate Apex and Flows during a Salesforce release?

Orchestrate Apex and Flows during a Salesforce release by enforcing an end-to-end deployment workflow that sequences metadata types properly. The process handles Flow activation automatically after deploying underlying objects, fields, and permissions.