Home / devops
Devops skills (70)
Delivery: source tracking, packaging, branching, CI/CD, environments and deployment troubleshooting.
- api-version-managementUse this skill when auditing, upgrading, or standardizing Salesforce API versions across metadata components, sfdx-project.json sourceApiVersion, Apex classes, LWC bundles, Aura bundles, and integration endpoints.
- appexchange-app-analyticsUse when an ISV partner needs usage telemetry for an AppExchange managed package — activating AppExchange App Analytics on a 1GP/2GP package, submitting AppAnalyticsQueryRequest records from the License Management Org, and downloading package usage logs...
- automated-regression-testingUse when building or maintaining automated end-to-end regression tests for Salesforce UI (Lightning, LWC, Aura, Flows), selecting a testing framework (UTAM, Provar, Selenium), handling Shadow DOM challenges, or scheduling regression suites.
- bitbucket-pipelines-for-salesforceUse this skill to set up, review, or troubleshoot Bitbucket Pipelines CI/CD workflows for Salesforce using SFDX JWT Bearer Flow or SFDP URL authentication, Apex test gates, branch-based deployment strategies, and Bitbucket repository variables for secret...
- change-set-deploymentUse when uploading, validating, or deploying a change set between Salesforce orgs through Setup UI.
- cicd-for-experience-cloudCI/CD pipeline patterns for Experience Cloud sites — the layer between sfdx-project metadata deploys and a working production site.
- code-coverage-orphan-class-cleanupUse when an org's overall Apex coverage is sliding toward 75% because of orphaned (uncovered, unreferenced) classes inflating the denominator.
- code-review-checklist-salesforceStructured Salesforce code review for Apex, triggers, async, and tests before merge or deployment — governor limits, bulk-safe triggers, CRUD/FLS and sharing posture, meaningful tests, and naming consistency.
- continuous-integration-testingUse when configuring Apex test execution in CI/CD pipelines, choosing test levels for deployments, parsing test results, or troubleshooting code coverage in automated builds.
- copado-essentialsUse when configuring or operating Copado Essentials deployment pipelines — including user story creation, branch management, promotion paths, conflict resolution, and choosing between Work Items and Pull Request deployment modes.
- cpq-deployment-administrationDeploying Salesforce CPQ (Steelbrick/SBQQ) configuration between orgs — Product Rules, Price Rules, Price Actions, Price Conditions, Option Constraints, Quote Templates, Custom Settings: data-migration strategy, parent-child ordering, external-ID mapping...
- cpq-deployment-patternsDeploying Salesforce CPQ configuration between environments in a CI/CD pipeline — required data record dependency order (Price Books > Products > Price Rules > Product Rules > Quote Templates), External ID cross-org matching, multi-pass deployment for...
- cross-cloud-deployment-patternsUse when sequencing a deployment that spans multiple Salesforce clouds — Sales Cloud, Service Cloud, and Experience Cloud — and encountering reference errors, cascading metadata failures, or DigitalExperienceBundle ordering problems.
- cumulusci-automationUse this skill when configuring CumulusCI (cci) for Salesforce project automation: authoring cumulusci.yml tasks and flows, customizing or composing standard flows, integrating Robot Framework acceptance tests.
- data-seeding-for-testingUse when creating test data for scratch orgs, sandboxes, or CI pipelines: Apex @testSetup factories, sf data import tree plans, CumulusCI datasets, Snowfakery. NOT for production data migration or ETL pipelines — use data/data-migration-planning.
- deployment-error-diagnosisPattern catalog of Salesforce metadata-deploy error strings and their fixes: `Cannot change type` of field, dependent-metadata ordering, profile / permission set delta issues, INVALID_CROSS_REFERENCE_KEY, missing-reference errors, inactive-flow and picklist...
- deployment-error-troubleshootingUse when a Salesforce metadata deployment fails and you need to diagnose the error from the DeployResult componentFailures.
- deployment-monitoringLive and historical status of a Salesforce metadata deployment: Metadata API checkDeployStatus, REST deployRequest polling, the Deployment Status Setup page, DeployResult status enum, component error triage, deploy queue concurrency, 30-day history limit.
- destructive-changes-deploymentManaging destructiveChanges.xml manifests for safe metadata deletion in Salesforce deployments.
- development-documentation-standardsStandards for Salesforce dev documentation — README, ADR, runbook, release note templates. Triggers: dev documentation standards, ADR template, runbook Salesforce. NOT for automated release notes — use devops/release-notes-automation.
- devops-center-advancedUse DevOps Center for work item tracking, org-based release pipelines, and merging into existing SFDX workflows. NOT for first-time setup — use admin/devops-process-documentation.
- devops-center-pipelineUse when setting up, managing, or troubleshooting a Salesforce DevOps Center pipeline — including pipeline stages, work items, bundles, promotions, conflict resolution, and GitHub connectivity.
- environment-specific-value-injectionUse this skill when configuring, reviewing, or troubleshooting how environment-specific values — endpoint URLs, client IDs, thresholds, feature flags — are managed across Salesforce orgs without hardcoding.
- environment-strategyUse when designing the full environment topology for a Salesforce program — selecting which org types to provision, how many, and how they map to your branching strategy and release pipeline.
- experience-cloud-deployment-adminDeploying an Experience Cloud site (formerly Community) between Salesforce orgs or sandboxes: metadata ordering, ExperienceBundle enablement, post-deployment publishing, change-set or SFDX-based migration.
- experience-cloud-deployment-devScripting or automating Experience Cloud site deployment between orgs with the Metadata API, sf CLI or CI/CD: ExperienceBundle (Aura sites), DigitalExperienceBundle (enhanced LWR sites), the ExperienceBundleSettings prerequisite, CMS content exclusion...
- feature-flag-custom-metadataImplement environment-safe feature flags using Custom Metadata Types for Apex, LWC, and Flow. NOT for user-level entitlements or permission sets — use admin/custom-metadata-types.
- flow-deployment-activation-orderingDeploying Flow metadata across environments when activation order matters: which flow version becomes active, how paused interviews survive deploys, avoiding the 'two active versions for a moment' race, SFDX / Metadata API deploy flags, 'Deploy as Active'...
- fsc-deployment-patternsUse when planning or executing metadata deployments for Financial Services Cloud (FSC) — including Person Account enablement sequencing, Account record-type ordering, Compliant Data Sharing (CDS) activation.
- git-branching-for-salesforceUse when selecting or reviewing a Git branching strategy for a Salesforce project — choosing between trunk-based development, GitFlow, or environment branching, and mapping branches to orgs, packages, and CI pipelines.
- github-actions-for-salesforceUse this skill to set up, review, or troubleshoot GitHub Actions CI/CD pipelines for Salesforce using SFDX JWT Bearer Flow authentication, Apex test gates, and branch-conditional deployments.
- gitlab-ci-for-salesforceUse this skill to set up, review, or troubleshoot GitLab CI/CD pipelines for Salesforce using SFDX JWT Bearer Flow authentication, Docker executor runners, Apex test gates, branch-based deployment jobs, and GitLab CI/CD variables for secret management.
- go-live-cutover-planningUse when planning, sequencing, or executing the final cutover to production for a Salesforce implementation or major release.
- health-cloud-deployment-patternsUse when planning or executing a Health Cloud deployment to production or a full sandbox, including managed package installation sequencing, Permission Set License assignment, care plan template setup, HIPAA compliance.
- isv-license-management-and-trialforceUse when an ISV partner is wiring license enforcement, trial provisioning, or feature-flag distribution into a managed package — covers License Management App (LMA) install and registration, Lead/License object.
- managed-package-developmentBuilding or maintaining Salesforce first-generation managed packages (1GP) for ISV distribution: namespace registration, packaging org structure, PostInstall/UninstallHandler Apex, push upgrades, Flow version management, subscriber org considerations.
- metadata-api-coverage-gapsUse this skill when a deployment, source push, or package version fails because a metadata type is unsupported, partially supported, or behaves differently across Metadata API, source tracking, unlocked packages, and 2GP managed packages.
- metadata-api-retrieve-deployMetadata API retrieve/deploy via sf CLI and package.xml: manifest authoring, destructiveChanges, deploy options (checkOnly, testLevel, rollbackOnError), CI scripting.
- metadata-diff-between-sandboxesUse when comparing metadata between two Salesforce orgs (UAT vs Prod, dev sandbox vs full copy, fork sandbox vs source) to surface drift, identify items needing deployment, or build a destructive-changes manifest.
- migration-from-change-sets-to-sfdxUse when planning or executing a migration from change-set-based deployments to Salesforce DX source-driven development.
- multi-package-developmentDesigning, orchestrating, and maintaining multi-package architectures in Salesforce DX: dependency DAG design, layered package decomposition, install ordering, cross-package API contracts, mono-repo vs multi-repo layout, and CI/CD sequencing for two or more...
- org-shape-and-scratch-definitionUse this skill when authoring, debugging, or optimizing a scratch org definition file (project-scratch-def.json): schema structure, features array, settings hierarchy, Org Shape sourcing, edition selection, orgPreferences-to-settings migration, and release...
- package-development-strategyDeciding between Salesforce package development approaches — unmanaged, unlocked, 1GP managed, 2GP managed — namespace selection, ISV distribution requirements, upgrade path design, AppExchange packaging strategy.
- packaging-dependency-graphModel and verify unlocked package dependencies, version pinning, and promotion. NOT for 1GP managed packages — use devops/multi-package-development.
- performance-testing-salesforceUse when planning or executing load tests, stress tests, or performance benchmarks against a Salesforce org.
- permission-set-deployment-orderingUse when deploying permission sets, permission set groups, or profiles and encountering cross-reference errors, silent permission loss, or ordering failures.
- pipeline-secrets-managementStore and inject Salesforce auth URLs, JWT keys, and API credentials into CI without leaking them.
- post-deployment-validationVerifying a Salesforce deployment worked after the metadata landed: quick deploy from a validated ID, Apex test result interpretation, Deployment Status page drill-down, functional smoke testing, JUnit/coverage output for CI, and rollback strategies.
- postman-for-salesforceUse when designing or auditing **Postman collections** that exercise Salesforce APIs — collection structure, OAuth authentication (Web Server, JWT bearer, Username-Password, Client Credentials), pre-request scripts that refresh access tokens, environment...
- pr-policy-templatesEnforce change quality via PR templates, required reviews, metadata ownership, and automated checks. NOT for branching model selection — use agentforce/agentforce-prompt-versioning.
- pre-deployment-checklistUse when preparing a Salesforce metadata deployment for production and need a structured gate-check before releasing.
- release-managementUse when planning, coordinating, or governing Salesforce releases: version numbering, rollback strategy, release notes, go/no-go criteria, release calendar, and sandbox preview alignment.
- release-notes-automationUse when generating customer- or stakeholder-facing release notes from git history, Jira/ADO ticket links, and Salesforce metadata diffs at deploy time.
- rollback-and-hotfix-strategyPlanning and executing metadata rollbacks and emergency hotfixes in Salesforce orgs.
- salesforce-cli-automationAutomating Salesforce work with the unified Salesforce CLI (`sf`, v2): shell scripts, Make/npm tasks, cron jobs and CI steps needing stable flags, `--json` output, org aliases, bulk/data commands, plugins, non-interactive auth.
- salesforce-code-analyzerUse this skill to configure and run Salesforce Code Analyzer v5 across PMD, ESLint, RetireJS, Regex, Flow, CPD, SFGE, and remote ApexGuru analysis for CI quality gates and AppExchange review preparation.
- salesforce-devops-tooling-selectionUse when a team needs to choose a DevOps tooling platform for Salesforce — comparing options like Gearset, Copado, Flosum, AutoRABIT, Blue Canvas, and Salesforce DevOps Center across axes of hosting model, team composition, compliance posture, and budget.
- salesforce-dx-project-structureUse this skill when setting up, configuring, or troubleshooting sfdx-project.json, organizing packageDirectories for mono-repo or multi-package projects, managing sourceApiVersion alignment, and structuring the standard source-format directory tree.
- sandbox-data-isolation-gotchasUse this skill when a sandbox has reached out to production systems, sent emails to real users, run live scheduled jobs, or leaked sensitive data after a refresh.
- sandbox-refresh-and-templatesSandbox refresh cycles, sandbox templates, post-refresh automation via the SandboxPostCopy Apex interface, and data handling during refresh. NOT for sandbox type selection — use admin/sandbox-strategy.
- scratch-org-managementUse this skill when designing, configuring, or troubleshooting scratch orgs: definition file structure, edition selection, allocation limits, Org Shape, CI automation via ScratchOrgInfo, and lifecycle management from the Dev Hub.
- scratch-org-poolsUse this skill when configuring pre-created scratch org pools for parallel CI testing, reducing pipeline wait times by claiming pre-warmed orgs instead of provisioning on demand.
- scratch-org-snapshotsUse Scratch Org Snapshots to reduce CI bring-up time from 10–20 minutes to under 2. NOT for persistent sandbox provisioning — use devops/scratch-org-pools.
- second-generation-managed-packages2GP managed package development: creating managed packages with Dev Hub and Salesforce CLI, semantic versioning, patch versions, namespace linking, ISV AppExchange listing, and subscriber upgrade management.
- sf-cli-plugin-authoringUse when authoring a custom Salesforce CLI (`sf`) plugin — internal team tooling that wraps deploy/test workflows, an ISV plugin distributed via npm, or migrating a legacy `sfdx`-style plugin to the v2 `sf` topic-and-command shape.
- sfdx-hardis-integrationAdopt sfdx-hardis for org monitoring, CI pipelines, and release automation. NOT for writing plugins to sfdx-hardis itself — use apex/sf-cli-and-sfdx-essentials.
- sfdx-monorepo-patternsStructure a single repo with multiple unlocked packages, shared templates, and cross-package test strategies. NOT for multi-repo org strategies — use apex/sf-cli-and-sfdx-essentials.
- source-tracking-and-conflict-resolutionUse when diagnosing and resolving SFDX source-tracking conflicts between a local project and a Salesforce org.
- unlocked-package-developmentUse this skill when designing, creating, versioning, or installing unlocked packages: package directory configuration in sfdx-project.json, namespace management, package dependencies, version lifecycle (beta to released), and subscriber installation.
- vscode-salesforce-extensionsUse this skill when setting up, configuring, or troubleshooting the Salesforce Extensions for VS Code: Apex Language Server activation, deploy-on-save behavior, Apex debugging, org authorization, and workspace project.