dx-devops-pipeline-manage
Use this skill to manage the full lifecycle of a DevOps Center pipeline — list all pipelines, get a single pipeline's details, create a new pipeline linked to a Git repository, add or remove stages, rename a stage, add or remove Salesforce environments on stages, attach or detach projects, and activate or deactivate the pipeline. Invoke when the user wants to set up a release pipeline, wire promotion stages across integration, UAT, staging, and production orgs, connect environments to stages, attach a project, or activate a continuous delivery pipeline. Uses sf devops pipeline and sf devops stage commands with --json output. DO NOT TRIGGER for work-item lifecycle, promotion or deployment execution, conflict detection, or standalone project creation (separate skills).
forcedotcom · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add forcedotcom/sf-skills --skill dx-devops-pipeline-manage技能说明
name: dx-devops-pipeline-manage description: "Use this skill to manage the full lifecycle of a DevOps Center pipeline — list all pipelines, get a single pipeline's details, create a new pipeline linked to a Git repository, add or remove stages, rename a stage, add or remove Salesforce environments on stages, attach or detach projects, and activate or deactivate the pipeline. Invoke when the user wants to set up a release pipeline, wire promotion stages across integration, UAT, staging, and production orgs, connect environments to stages, attach a project, or activate a continuous delivery pipeline. Uses sf devops pipeline and sf devops stage commands with --json output. DO NOT TRIGGER for work-item lifecycle, promotion or deployment execution, conflict detection, or standalone project creation (separate skills)." metadata: version: "1.0" domains: ["Developer Experience"] minApiVersion: "58.0" relatedSkills: - "dx-devops-work-item-manage" accessCheck: - type: "orgPref" value: "ALMDevopsCorePref" - type: "userPerm" value: "UserHasDevOpsCore" cliTools: - tool: ["jq"] semver: ">=1.6" - tool: ["sf"] semver: ">=2.0.0"
DevOps Center Pipeline Management
Manages the complete pipeline lifecycle in DevOps Center — from creation against a repository, through stage and environment configuration and project attachment, to activation of a ready-to-promote release pipeline. Provides headless CLI-driven operations for autonomous release workflows.
Scope
- In scope: List pipelines, get pipeline details, create a pipeline (linked to an existing or new Git repo), add/delete/rename stages, add/delete Salesforce environments on stages, attach/detach projects, and activate/deactivate/rename the pipeline
- Out of scope: Work-item lifecycle, promotion/deployment execution, conflict detection, standalone project creation (separate skills)
Required Inputs
Gather or infer before proceeding:
- Operation type: list, get, create, add-stage, delete-stage, rename-stage, add-environment, delete-environment, attach-project, detach-project, activate, or deactivate
- For get / any stage or environment op: pipeline ID (required) — obtain via
sf devops pipeline list --json - For create: pipeline name (required) and a Git repo (
--repo, required). Repo flags differ by scenario:- Existing repo (GitHub or Bitbucket): only
--repo <url>— do not pass--repo-type/--create-repo - New GitHub repo:
--repo <name> --create-repo --repo-type github --repo-owner <org-or-user> - New Bitbucket repo:
--repo <name> --create-repo --repo-type bitbucket --bitbucket-workspace <workspace>(--bitbucket-project-key <key>optional) - Description (
--description) optional in all cases
- Existing repo (GitHub or Bitbucket): only
- For add-stage: pipeline ID, new stage name, and
--next-stage-id(the stage the new one precedes) — get stage IDs viasf devops pipeline get - For add-environment: pipeline ID, stage ID, environment name, and
--org-type(Production or Sandbox) - For attach/detach-project: pipeline ID and project ID
- For activate/deactivate/rename: pipeline ID
Defaults unless specified:
- Output format:
--jsonfor headless consumption - Target org: use
--target-org <alias>if not relying on the default org
If the user gives a clear request ("create a pipeline on repo myorg/myrepo", "add a UAT stage before Production", "activate pipeline 0XB..."), proceed immediately without unnecessary questions.
Workflow
All operations use sf devops pipeline and sf devops stage CLI commands with --json output for structured consumption. Pipeline IDs and stage IDs are the primary identifiers — resolve them via list and get before mutating.
Phase 1 — Identify Operation
- Determine the operation type from user intent:
- "list", "show all pipelines" → list; "details of pipeline", "show stages" → get
- "create", "set up", "new pipeline" → create
- "add stage", "insert stage" → add-stage; "rename stage" → rename-stage; "remove/delete stage" → delete-stage
- "connect environment", "add org to stage" → add-environment; "remove environment" → delete-environment
- "attach project", "connect project" → attach-project; "detach project" → detach-project
- "activate", "turn on"; "deactivate", "turn off"; "rename pipeline" → lifecycle update
Phase 2 — Execute Operation
-
Verify org authentication before any operation:
sf org display --json- If no default org is set or auth has expired, instruct the user to run
sf org login web --set-default --alias <alias> - Confirm the org has DevOps Center enabled by running
sf devops pipeline list --json - Add
--target-org <alias>to every command when targeting a specific org
- If no default org is set or auth has expired, instruct the user to run
-
Inspect pipelines:
sf devops pipeline list --json # all pipelines in the org sf devops pipeline get --pipeline-id <pipeline-id> --json # one pipeline, with stages/repos/projectslistreturns SObject records under.result.pipelines[]with capitalized fields (.Id,.Name,.IsActive) — it does not include stages or connected projectsgetreturns a single pipeline under.resultwith camelCase fields (.id,.name,.stages[],.connectedProjects[]); each stage has.id,.name,.nextStageId,.branchName, and.environment.{id,name}. Stages are a linked list — order is defined bynextStageId, and the terminal stage hasnextStageId: null. Usegetto discover stage IDs before any stage or environment operation
-
Create a pipeline — the pipeline must be linked to a Git repository.
--nameand--repoare always required; the remaining flags depend on the repo scenario:# Existing repo (GitHub or Bitbucket) — pass the full repo URL, nothing else sf devops pipeline create --name "<pipeline-name>" --repo <repo-url> --