Dx Devops Work Item Manage
Use this skill to manage the full lifecycle of DevOps Center work items, list, create...
Install
npx skills add forcedotcom/sf-skills --skill dx-devops-work-item-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
- No, instructions only
What it does
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 changes to work item branches, through the DevOps Center commit API or git. 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, or create a pull request for code review. Consolidates sf devops work-item and review operations. DO NOT TRIGGER for promotion or deployment operations, or conflict detection.
DevOps Center Work Item Management
Manages the complete work item lifecycle in DevOps Center, from creation through status transitions to promotion readiness. Provides headless CLI-driven operations for autonomous release workflows.
Scope
- In scope: List work items, create new work items, commit changes to work item branches, update work item fields (subject, description, status), transition work item status (New → In Progress → Ready to Promote), create pull requests for work item branches
- Out of scope: Promotion/deployment, conflict detection, pipeline or project management (separate skills)
Required Inputs
Gather or infer before proceeding:
- Operation type: list, create, update, commit, or create-review
- For list: project ID (required), obtain via
sf devops project list --jsonif not provided - For create: project ID (required), subject (required), description (optional)
- For commit: work item name or ID (required), commit message, and either the files to commit (git path) or the components to commit (API path). Optional: dev org alias, the org that holds the changes. When provided, try the DevOps Center commit API first (see step 5); otherwise use git
- For update: work item name (e.g., WI-000001) or work item ID (required), fields to update (subject, description, status)
- For create-review: work item name (e.g., WI-000001) or work item ID (required)
Defaults unless specified:
- Output format:
--jsonfor headless consumption - Work item identifier: prefer
--work-item-name(WI-000001) over--work-item-idwhen both are available (names are human-readable)
If the user provides a clear request ("list work items for Project Alpha", "create work item to fix login bug", "move WI-12345 to In Progress", "create PR for WI-12345"), proceed immediately without unnecessary questions.
