sf-deployment-constraints

Enforce validation-only Salesforce deployments with test coverage and dependency ordering.

13|2|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/jiten-singh-shahi/salesforce-claude-code --skill sf-deployment-constraints
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sf-deployment-constraints
Source: https://github.com/jiten-singh-shahi/salesforce-claude-code/tree/main/.cursor/skills/sf-deployment-constraints
Command: npx skills add https://github.com/jiten-singh-shahi/salesforce-claude-code --skill sf-deployment-constraints

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevent risky, partial, or failed Salesforce deployments by enforcing a validation-first workflow, adequate test coverage, correct metadata ordering, and rollback readiness so teams avoid broken production state and deployment-induced outages.

Core Features & Use Cases

  • Validation-first enforcement: Require validation-only deploys before any real deploy and prohibit quick-deploy without an explicit job id when conditions aren't met.
  • Test coverage and test-level gating: Mandate appropriate test-level flags for shared orgs and production and ensure aggregate org coverage meets the production threshold.
  • Dependency ordering and safe packaging: Recommend and enforce an ordered deployment sequence (objects, fields, layouts, Apex, permission sets, profiles last) and separate Profile deployments.
  • Rollback and snapshot readiness: Require pre-deploy snapshots for destructive changes and prescribe rollback strategies like git revert, single-file restore, or package version rollback.
  • Use Case: Use when promoting code from CI/UAT to production to prevent silent test omissions, broken metadata references, and unrecoverable destructive changes.

Quick Start

Validate the package with a validation-only deploy using the appropriate test level, review the validation report, and then quick-deploy by job id once tests and dependencies are confirmed.

Frequently Asked Questions about sf-deployment-constraints

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

FAQPage Schema
How do I enforce validation-only deploys before promoting Salesforce metadata to production?▼

Salesforce deployment validation is enforced by requiring validation-only deploys before any real deploy. This workflow prohibits quick-deploy without an explicit job id, ensuring tests and dependencies are confirmed before promoting metadata changes.

What test coverage gates are required for Salesforce production deployments?▼

Salesforce deployment test coverage gates mandate appropriate test-level flags for shared orgs and production. They ensure aggregate org coverage meets the production threshold, preventing silent test omissions during CI/UAT to production promotions.

How do I order metadata dependencies for safe Salesforce deployments?▼

Safe Salesforce deployments require ordered metadata sequences: objects, fields, layouts, Apex, permission sets, and profiles last. Separating Profile deployments prevents broken metadata references and deployment failures caused by incorrect dependency ordering.

How do I create a rollback plan for destructive Salesforce metadata changes?▼

Rollback plans for destructive Salesforce changes require pre-deploy snapshots. Prescribed rollback strategies include git revert, single-file restore, or package version rollback to avoid unrecoverable destructive changes and broken production state.

Can I use quick-deploy for Salesforce metadata without a validation job id?▼

Quick-deploy for Salesforce metadata is prohibited without an explicit job id when deployment conditions are not met. This constraint enforces a validation-first workflow, requiring validation reports to be reviewed and confirmed before quick-deploying by job id.

Why do Salesforce deployments fail during CI/CD promotions and how can I prevent them?▼

Salesforce deployments fail during CI/CD promotions due to silent test omissions, broken metadata references, and partial deployments. Prevent these risky failures by enforcing validation-first workflows, test coverage gating, and dependency ordering before production promotion.