forcedotcom/sf-skills / plugins/builder/salesforce-development/skills/dx-org-manage
dx-org-manage
VerifiedUse to EXECUTE Salesforce org operations immediately via the sf CLI (this skill runs them, it does NOT generate scripts): create scratch orgs (from edition, definition file, snapshot, or org shape), list/display/resume/delete scratch orgs, open orgs in browser. Trigger: 'create scratch org', 'create org from snapshot', 'delete scratch org', 'open my org'. Do NOT use for switching the default org (use dx-org-switch), deploying metadata (use platform-metadata-deploy), or creating/checking/listing/deleting org snapshots (use dx-org-snapshot-manage).
references/snapshot_usage.md
View on GitHub# Using Snapshots in Scratch Org Definition Files
After creating a snapshot, reference it in scratch org definition files to create new scratch orgs from the saved state.
## Scratch Org Definition File Format
Use the `snapshot` field instead of `edition` in your `project-scratch-def.json`:
```json
{
"orgName": "My Company",
"snapshot": "MySnapshot",
"features": ["EnableSetPasswordInApi"],
"settings": {
"lightningExperienceSettings": {
"enableS1DesktopEnabled": true
}
}
}
```
## Key Differences from Edition-Based Definitions
| Field | Edition-based | Snapshot-based |
|-------|--------------|----------------|
| Primary field | `"edition": "Developer"` | `"snapshot": "MySnapshot"` |
| Contents | Empty org with edition defaults | Pre-configured org state from snapshot |
## Creating a Scratch Org from Snapshot
```bash
sf org create scratch --definition-file config/project-scratch-def.json --alias from-snapshot
```
The scratch org will be created with all the metadata, data, and configuration from the snapshot.
## Common Use Cases
### 1. Package Development
```json
{
"orgName": "Package Dev Org",
"snapshot": "Dependencies_v1.2.0",
"description": "Org with all dependencies installed"
}
```
### 2. Testing Baseline
```json
{
"orgName": "Test Baseline",
"snapshot": "TestData_Populated",
"description": "Org with sample data for testing"
}
```
### 3. CI/CD Pipeline
```json
{
"orgName": "CI Scratch Org",
"snapshot": "Nightly_Build_Baseline",
"description": "Latest nightly build dependencies"
}
```
## Workflow Summary
1. **Create snapshot**: `sf org create snapshot --source-org <scratch> --name MySnapshot`
2. **Check status**: `sf org get snapshot --snapshot MySnapshot`
3. **Reference in definition file**: `"snapshot": "MySnapshot"`
4. **Create new scratch org**: `sf org create scratch --definition-file config/project-scratch-def.json`
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |