sf-deploy

Use this skill when the user needs deployment orchestration : dry-run validation, targeted or manifest-based deploys, CI/CD workflow advice, scratch-org management, failure triage, or safe rollout sequencing for Salesforce metadata. Use sf-deploy when the work involves: Delegate elsewhere when the user is: This ordering prevents many dependency and FLS failures. Ask for or infer: Preflight checks: Confirm auth, repo shape, package directories, and target scope. Use manifest- or metadata-scoped validation when the change set is targeted. After a successful validation, guide the user to the correct next action: Then verify tests, Flow state, permission assignments, and smoke-test behavior. Summarize what deployed, what failed, what was skipped, and what the next safe action is. Output template: references/deployment-report-template.md Full workflows: references/orchestration.md , references/trigger-deployment-safety.md Default pipeline shape: Static analysis now uses Code Analyzer v5 ( sf code-analyzer ), not retired sf scanner . Deep reference: references/deployment-workflows.md Use this skill to orchestrate deployment/publish sequencing around agents, but use the agent-specific skills for authoring decisions: For full agent DevOps details, including Agent: pseudo metadata, publish/activate, and sync-between-orgs, see: - sf project deploy start , quick , report , or retrieval...