Dx Devops Pipeline Manage
Use this skill to manage the full lifecycle of a DevOps Center pipeline, list all...
Install
npx skills add forcedotcom/sf-skills --skill dx-devops-pipeline-manage -g -a claude-code -y- Repository
- forcedotcom/sf-skills1.1k
- Category
- DevOps
- Updated
- 5d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- Yes, review before use
What it does
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).
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
