forcedotcom/sf-skills / skills/dx-lifecycle-center
dx-lifecycle-center
VerifiedLifecycle Center for DX Inspector and Builder Central. Four jobs: (A) list the orgs connected to DX Inspector; (B) connect a new org (sandbox or scratch, production, OrgFarm) as a deploy target; (C) connect or check the Lifecycle Center org, also written LifecycleCenter, lifecycle-center, ALMDevOpsCenterHub, or Hub org; (D) deploy, validate, or quick-deploy components that already exist in the user's org to a connected org, and poll a simple-deploy requestId. TRIGGER on: show, list, or pick connected orgs or environments; connect, add, log in to, or repair an org; connect the Lifecycle Center org; deploy, validate, push, or publish components (metadata) to another org, URL, org id, alias, or environment name. Short asks like "connect a new org" or "deploy to my sandbox" match. NOT for promoting work items (dx-devops-promote), local source deploys (platform-metadata-deploy), or publishing sites or packages. Deploys move components between orgs, not local files.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.1 KB |
| examples/workflows.md | markdown | 12.0 KB |
| references/connect-api.md | markdown | 9.6 KB |
| references/connect-org.md | markdown | 19.8 KB |
| references/deploy.md | markdown | 12.1 KB |
| references/error-handling.md | markdown | 2.7 KB |
| references/hub-org.md | markdown | 6.5 KB |
| references/list-orgs.md | markdown | 11.8 KB |
| references/request-body.md | markdown | 3.7 KB |
| references/troubleshooting.md | markdown | 8.4 KB |
| scripts/hub-get.shexecutable | script | 2.8 KB |
| scripts/poll-deploy-status.shexecutable | script | 9.3 KB |
| scripts/resolve-environment.shexecutable | script | 16.3 KB |
references/request-body.md
View on GitHub# Simple Deploy Request Body
> **Scope:** the skill sends metadata only. `datachanges` is documented here for reference but is deferred; do not send it from this skill yet.
Source of truth: `ISimpleDeployResource` / `SimpleDeployInputRepresentation` (Connect) and the cliaas `validator/schema.ts`. Connect forwards `requestBody` to cliaas unchanged, so cliaas validation errors surface as a 400.
## Envelope (Connect input)
| Field | Type | Notes |
|---|---|---|
| `namedCredential` | string | `DevopsEnvironment.NamedCredential`. Must be bound to `targetEnvironmentId`. |
| `targetEnvironmentId` | string | `DevopsEnvironment.Id`. Scopes validate and quick-deploy tracking. |
| `requestBody` | object | The deploy payload below. |
| `headerTargetInstanceURL`, `headerTargetAccessToken` | string | Raw-token alternative to `namedCredential`. **Do not use from this skill.** |
| `components` | array | Deprecated and ignored. Do not send. |
## `requestBody`
| Field | Type | Notes |
|---|---|---|
| `changes[]` | `{fullName, type, operation}` | All three required and non-blank. `operation` is `add`, `modify`, or `delete`. Map anything else (dependency, manual, manifest) to `modify`. |
| `datachanges` | object (deferred) | `{ "objectsList": { "<ObjectApiName>": { "fields": [{"name": "..."}], ... } } }`. Each object needs at least one field. |
| `isCheckDeploy` | boolean | `true` = validate only (alias `checkOnly`). Default `false`. |
| `testOptions` | `{level, tests[]}` | `level`: `NoTestRun`, `RunSpecifiedTests`, `RunLocalTests` (default), `RunAllTestsInOrg`. `tests` must list the tests for `RunSpecifiedTests`; send an empty array otherwise. Legacy `testLevel` + `tests` also accepted. |
| `isQuickDeploy` | boolean | `true` = deploy a prior validation. Default `false`. |
| `checkDeployIdentifier` | string | `0Af` id (15 or 18 chars). Required with `isQuickDeploy`. |
| `metadataLookups` | map<string,string> | Optional. |
### `datachanges.objectsList.<Object>` entry
`fields[]` (required, `{name, ...}`), plus optional `relatedObjects`, `duplicateCheck` (field names for dedupe), `recordIds`, `filters`, `formats`, `numRecords`, `externalIdField` (upsert/match key, for example `External_Account_Id__c`). Unknown keys pass through. Remove duplicate fields by `name` before sending.
## Mode matrix
| Mode | `changes` | `datachanges` | `testOptions` | Other |
|---|---|---|---|---|
| deploy | required (this skill) | deferred | optional | The API itself allows data-only; this skill sends metadata. |
| validate | **required** | ignored (stripped, remembered for quick deploy) | optional | `isCheckDeploy: true`. |
| quickDeploy | **forbidden** | forbidden | **forbidden** | `isQuickDeploy: true` + `checkDeployIdentifier`. |
Test level default: Production targets need tests to complete a deploy, so use `RunLocalTests`; sandbox and scratch-like targets use `NoTestRun`. An explicit user choice always wins.
## Examples
Metadata deploy:
```json
{
"namedCredential": "QA_Sandbox_1PJSB...",
"targetEnvironmentId": "1QeSB0000004T3R0AU",
"requestBody": {
"changes": [
{"fullName": "AccountService", "type": "ApexClass", "operation": "modify"},
{"fullName": "Account.Tier__c", "type": "CustomField", "operation": "add"}
],
"testOptions": {"level": "NoTestRun", "tests": []}
}
}
```
Validate only:
```json
{ "namedCredential": "Prod", "targetEnvironmentId": "1Qe...",
"requestBody": { "isCheckDeploy": true,
"changes": [{"fullName": "AccountService", "type": "ApexClass", "operation": "modify"}],
"testOptions": {"level": "RunLocalTests", "tests": []} } }
```
Quick deploy:
```json
{ "namedCredential": "Prod", "targetEnvironmentId": "1Qe...",
"requestBody": { "isQuickDeploy": true, "checkDeployIdentifier": "0AfXXXXXXXXXXXXXXX" } }
```
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: 323k | 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 |