salesforce-deploy
Use when deploying Salesforce metadata — package.xml, source-format/metadata-format, validate, deploy, diff, rollback, scratch orgs, sandboxes, production.
What this skill does
# Salesforce deploy skill ## Source vs metadata format - **Source format** (sfdx, default): one file per metadata type, friendly to git - **Metadata format** (legacy): single `package.xml` + folder structure, used for production deploys via change sets / migration tool ## Standard flow (sfdx) ```bash # auth sf org login web -a my-sandbox # validate (no commits, runs tests) sf project deploy validate --source-dir force-app --test-level RunLocalTests --target-org my-sandbox # deploy (after validate passes) sf project deploy start --source-dir force-app --test-level RunLocalTests --target-org my-sandbox # quick deploy from a validated package sf project deploy quick --job-id 0Af... --target-org my-sandbox ``` ## Diff before deploy ```bash # what's different from the org? sf project retrieve preview --target-org my-sandbox --source-dir force-app sf project deploy preview --target-org my-sandbox --source-dir force-app ``` Always preview before a prod deploy. The preview reports adds/changes/deletes. ## Tests - `--test-level NoTestRun` — only sandboxes, never prod - `--test-level RunSpecifiedTests --tests MyTest1,MyTest2` — fastest validation - `--test-level RunLocalTests` — required for production deploys (skips managed-package tests) - `--test-level RunAllTestsInOrg` — slow, only when needed for compliance ## Rollback There is no native rollback in Salesforce. Strategies: - Tag the previous successful deploy SHA in git - Validate the previous version against the org and quick-deploy it on failure - Pre-deploy: take metadata snapshot via `sf project retrieve start --metadata <list>` ## Common deploy errors - **`Cannot find component`** — destructive change order issue. Use destructive changes pre-deploy. - **`Test coverage failure`** — run `sf apex run test --code-coverage` locally, find < 75% classes. - **`Field not visible`** — profile/permset diff between source and target org. - **`InvalidCrossReference`** — referenced record id doesn't exist in target org. Use `sf data import` for reference data. ## Scratch orgs ```bash sf org create scratch --definition-file config/project-scratch-def.json --alias my-scratch --duration-days 7 sf project deploy start --source-dir force-app --target-org my-scratch ``` ## CI/CD pattern 1. PR opens → validate against integration sandbox with `--test-level RunLocalTests` 2. PR merged → deploy to integration sandbox with `--quick` from validated job-id 3. Release branch → validate against UAT 4. UAT signoff → quick-deploy to production
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.