sf-deploy

Automate Salesforce metadata deployment and validation workflows with sf CLI v2.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/dcinzona/folios --skill sf-deploy-dcinzona
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sf-deploy
Source: https://github.com/dcinzona/folios/tree/main/.agents/skills/sf-deploy
Command: npx skills add https://github.com/dcinzona/folios --skill sf-deploy-dcinzona

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Orchestrates and hardens Salesforce metadata deployments so teams can validate, deploy, and verify changes reliably without risking production outages or dependency errors.

Core Features & Use Cases

  • Deployment orchestration: supports dry-run validation, manifest- or source-dir deploys, quick-deploys, status reporting, and cancellation workflows to minimize risk.
  • Release sequencing and safety: prescribes deploy ordering (objects → permission sets → Apex → flows → activation), test-level guidance, and post-validation handoff to data or agent workflows.
  • CI/CD and agent support: provides pipeline patterns, agent publish/activate sequencing, and troubleshooting guidance for Agentforce and other integrated metadata types.
  • Use case: validate a release with --dry-run, review results, quick-deploy the validated job ID, then assign permission sets and run smoke tests.

Quick Start

Validate your force-app using a dry-run deploy to the target org alias and then run the recommended next action based on the validation outcome.

Frequently Asked Questions about sf-deploy

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

FAQPage Schema
How do I validate Salesforce metadata changes before deploying to production?

You can validate Salesforce metadata changes using a dry-run deployment with the sf CLI. This process checks dependencies and test results against the target org without committing changes, ensuring safe production releases.

What is the correct deployment sequence for Salesforce metadata?

The recommended Salesforce metadata deployment sequence is objects, permission sets, Apex, flows, and then activation. Following this order prevents dependency errors and ensures components resolve correctly during release.

How do I use a validated deployment ID for a quick deploy in Salesforce?

After running a successful dry-run validation, you use the resulting job ID to execute a quick deploy. This skips redundant testing and rapidly pushes the previously validated Salesforce metadata to the target org.

Can I deploy Salesforce metadata to non-source-tracking orgs using sf CLI?

Yes, you can deploy Salesforce metadata to both source-tracking and non-source-tracking orgs. The workflow supports manifest-based and source-dir deployments, explicitly defining scopes for reliable sf CLI v2 operations.

How do I publish and activate Agentforce metadata during a deployment?

Agentforce metadata deployment follows a specific publish and activate sequencing workflow. After deploying the base metadata, you execute the prescribed Agentforce activation flow to ensure the agent functions correctly.

What should I do after a Salesforce metadata deployment completes?

Post-deployment handoff procedures include assigning permission sets to users and running smoke tests. These steps verify the Salesforce metadata functions correctly in the target org environment.