AI Summarysf-deploy automates Salesforce DevOps workflows including metadata deployments, org management, and CI/CD pipeline setup using Salesforce CLI v2. Developers managing Salesforce projects benefit from guided deployment automation and troubleshooting.
Install
# Add to your project root as SKILL.md curl -o SKILL.md "https://raw.githubusercontent.com/Jaganpro/sf-skills/main/skills/sf-deploy/SKILL.md"
Description
Salesforce DevOps automation using sf CLI v2. TRIGGER when: user deploys metadata, creates/manages scratch orgs or sandboxes, sets up CI/CD pipelines, or troubleshoots deployment errors with sf project deploy. DO NOT TRIGGER when: writing Apex/LWC code (use sf-apex/sf-lwc), creating metadata XML (use sf-metadata), or querying org data (use sf-data).
Prerequisites
Before deployment, verify: `bash sf --version # Requires v2.x sf org list # Check authenticated orgs test -f sfdx-project.json # Valid SFDX project `
sf-deploy: Comprehensive Salesforce DevOps Automation
Expert Salesforce DevOps engineer specializing in deployment automation, CI/CD pipelines, and metadata management using Salesforce CLI (sf v2).
Core Responsibilities
• Deployment Management: Execute, validate, and monitor deployments (metadata, Apex, LWC) • DevOps Automation: CI/CD pipelines, automated testing, deployment workflows • Org Management: Authentication, scratch orgs, environment management • Quality Assurance: Tests, code coverage, pre-production validation • Troubleshooting: Debug failures, analyze logs, provide solutions ---
⚠️ CRITICAL: Orchestration Order
` ┌─────────────────────────────────────────────────────────────────────────────┐ │ sf-metadata → sf-flow → sf-deploy → sf-data │ │ ▲ │ │ YOU ARE HERE │ └─────────────────────────────────────────────────────────────────────────────┘ ` Deploy order WITHIN sf-deploy: Objects/Fields → Permission Sets → Apex → Flows (Draft) → Activate Flows | Phase | Metadata Type | Why This Order | |-------|---------------|----------------| | 1 | Custom Objects/Fields | Everything references these | | 2 | Permission Sets | FLS requires fields to exist | | 3 | Apex Classes | @InvocableMethod needed before Flows | | 4 | Flows (as Draft) | Flows reference fields and Apex | | 5 | Activate Flows | Safe to activate after validation | See references/orchestration.md for detailed deployment workflows and agent deployment patterns. ---
Quality Score
Good
84/100
Trust & Transparency
Open Source — MIT
Source code publicly auditable
Verified Open Source
Hosted on GitHub — publicly auditable
Actively Maintained
Last commit Today
125 stars — Growing Community
23 forks