Use this skill to manage the full lifecycle of DevOps Center work items — list, create, update, commit changes, perform status transitions, and create pull requests. Update fields like subject, description, and status. Commit and push code changes to work item branches. Create pull requests for work item branches via DevOps Center API. Invoke when the user wants to track, find, create, or update a work item, commit changes to a work item branch, advance a work item's status through the pipeline,
dx-devops-work-item-manage is an official Salesforce skill for managing the full lifecycle of DevOps Center work items through headless, CLI-driven operations. It solves the problem of tracking and moving change through a Salesforce release pipeline: listing, creating, and updating work items, committing code to work-item branches, transitioning status (New → In Progress → Ready to Promote), and opening pull requests for review — all via the `sf devops work-item` commands with `--json` output for structured, autonomous consumption. It deliberately excludes promotion/deployment, conflict detection, and pipeline or project management, which are handled by separate skills.
The workflow first identifies the operation from user intent (list, create, commit, update, or create-review), then verifies org authentication with `sf org display --json` and, if needed, instructs the user to run `sf org login web`. List operations require a project ID (resolvable via `sf devops project list`), parse the `.result[]` array, and can filter by status with jq. Create operations capture the returned work-item name, branch, and environment and are idempotent against duplicate subjects. Commit operations use a standard git flow (checkout, add, commit, push) against the work item's dedicated feature branch, and update operations change subject, description, or status. Required tooling is documented as sf >= 2.0.0, git >= 2.0.0, and jq >= 1.6, targeting API version 58.0+.
The target users are Salesforce developers and release engineers running DevOps Center, especially those building autonomous or headless release workflows. Authentication is handled entirely through the official Salesforce CLI web login, and operations are scoped, standard developer actions (git commits and API-driven work-item updates) rather than anything destructive.
Listing, creating, and updating DevOps Center work items; committing and pushing code to a work item's branch; transitioning status through the pipeline (New → In Progress → Ready to Promote); and creating pull requests for code review. It consolidates sf devops work-item and review operations.
It does not handle promotion or deployment, conflict detection, or pipeline/project management — those are separate skills. The description tells the agent not to trigger for those cases.
The Salesforce CLI (sf >= 2.0.0), git >= 2.0.0, and jq >= 1.6, with a minimum Salesforce API version of 58.0. Authentication is via `sf org login web`.
DevOps Center creates a dedicated feature branch per work item. The skill uses a standard git flow — checkout the branch, add files, commit with a message, and push — and changes must be committed before a work item can be marked Ready to Promote or have a PR created.
Yes. It verifies the org session with `sf org display --json` and, if no default org is set or the session expired, directs the user to authenticate with the official `sf org login web` command. No credentials are handled outside the Salesforce CLI.
Quick Setup:
.claude/skills/Repository
forcedotcom/sf-skills