schema-migrate
Use for Salesforce schema changes — object/field/relationship migrations w/ deploy plan, sandbox validation, rollback strategy. Different from /migrate (data) — schema-migrate handles metadata.
What this skill does
# schema-migrate
Salesforce schema migration. Metadata-shaped. Plan + validate + deploy + verify.
## When this differs from /migrate
- `/migrate` — data migration (rows between systems / shapes)
- `/schema-migrate` — metadata migration (objects, fields, relationships in Salesforce)
## Method
1. **Source state.** What does the current org's schema look like for the target objects?
2. **Target state.** What's the desired shape — fields added, types changed, relationships modified, picklists updated?
3. **Diff.** Per object:
- Fields added / removed / type-changed
- Relationships altered
- Picklist values changed
- Validation rules / triggers affected
4. **Risk per change:**
- **Breaking** — existing data won't fit new schema (e.g. shrinking field length, removing required field)
- **Lossy** — data must be transformed before migration (e.g. text → picklist)
- **Safe** — additive only
5. **Deploy plan:**
- **Pre-deploy:** data backup or transform of soon-to-be-incompatible records
- **Schema deploy:** sfdx package deploy
- **Post-deploy:** verify counts, sample integrity, rerun automation tests
6. **Rollback strategy:** explicit per change (some metadata changes don't roll back cleanly — flag those)
## Output shape
```
# Schema migration plan
## Diff
| Object | Field | Change | Risk |
|---|---|---|---|
| Account | Industry__c | text(255) → picklist | Lossy — 12 distinct values exist |
| Contact | Phone__c | added | Safe |
| Order__c | Total__c | currency → number | Breaking — currency loses ISO context |
## Pre-deploy
- Run: SELECT Industry__c, COUNT(Id) FROM Account → 14 distinct values; map to 8 picklist values
- Backup: sf project retrieve start --metadata Account → snapshot
## Schema deploy
- Validate: sf project deploy validate --source-dir force-app --test-level RunLocalTests
- Preview: sf project deploy preview --source-dir force-app --target-org prod
- Deploy: (after validation green + preview reviewed)
## Post-deploy
- Reconciliation queries:
- Account count parity
- Industry__c picklist distribution matches mapping
- Smoke test: 5 sample records open in UI without error
## Rollback
- Account.Industry__c text→picklist: NOT cleanly reversible. Restore from backup.
- Contact.Phone__c add: removable in next deploy.
- Order__c.Total__c type change: lossy reversal. Restore from backup.
## Effort estimate
- Pre-deploy data transform: 4 hours
- Validation deploy: 30 min
- Production deploy window: 1 hour
- Total: ~6 hours
```
## Rules
- **Cite metadata files.** Every change refers to a `.field-meta.xml`, `.object-meta.xml`, etc.
- **Flag non-reversible changes loudly.** Type narrowing, field removal, picklist value deletion.
- **Pre-deploy data transform** mandatory for any lossy change.
- **Validate before deploy.** No exceptions in production.
- **Reconciliation queries** for every breaking change.
## Anti-patterns
- Deploying a breaking schema change without pre-deploy data transform
- "We'll deal with rollback if needed"
- Skipping validation deploy ("it worked in dev")
- Picklist value deletion without checking dependent records
## When NOT to use
- Pure data move (no schema change) — `/migrate`
- Greenfield org (no existing data to migrate) — direct deploy
- Non-Salesforce — different stack entirely
## Subagent dispatch
- `salesforce-architect` agent for the diff + risk pass
- `Bash` for sfdx commands
- Memory MCP for prior schema-migration patterns
## Value over native CC
CC will deploy SF metadata on request. CC won't naturally produce a structured diff × risk × pre-deploy × rollback plan with reconciliation queries. The Salesforce-specific framing IS the value.
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.