devops-workitem-update
Skill0 starsChanged 3 months agoMITView on GitHub
Update Azure DevOps work item fields (Description, Acceptance Criteria, State, etc.)
In this repository27 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- buildSkill
- cleanup-worktreeSkill
- db-querySkill
- db-searchSkill
- dd-errorsSkill
- devops-wiki-updateSkill
- devops-workitem-createSkill
- devops-workitem-readSkill
- finalize-taskSkill
- find-codeSkill
- merge-mainSkill
- panel-review-fixSkill
- panel-reviewSkill
- prSkill
- rebase-mainSkill
- starttaskSkill
- testSkill
- ask-codexSkill
- ask-geminiSkill
- councilSkill
- dailySkill
- find-sessionSkill
- merged-prsSkill
- mm-notifySkill
- optimize-promptSkill
- qSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Ask the user what to update (or infer from context)
- Distinctive: line 15
Update the work item via PowerShell:
- Very specific: line 26
Important: Use ConvertTo-Json -InputObject $ops (not piping) to preserve single-element arrays.
- Very specific: line 28
Verify: check that rev incremented in response, show link
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Update Azure DevOps Work Item
Work item ID: $ARGUMENTS
Process
- Ask the user what to update (or infer from context)
- Update the work item via PowerShell:
$ops = @(
@{ op = "add"; path = "/fields/System.Title"; value = "New title" }
@{ op = "add"; path = "/fields/System.Description"; value = "<p>HTML content</p>" }
)
$body = ConvertTo-Json -InputObject $ops -Depth 5
Invoke-RestMethod -Uri "https://devops.example.com/DefaultCollection/MyProject/_apis/wit/workitems/$ARGUMENTS`?api-version=6.0" -Method Patch -Body $body -ContentType "application/json-patch+json" -UseDefaultCredentialsImportant: Use ConvertTo-Json -InputObject $ops (not piping) to preserve single-element arrays.
- Verify: check that
revincremented in response, show link
Field Reference
| Field | Path |
| Title | /fields/System.Title |
| Description | /fields/System.Description |
| Acceptance Criteria | /fields/Microsoft.VSTS.Common.AcceptanceCriteria |
| State | /fields/System.State |
| Assigned To | /fields/System.AssignedTo |
| Area Path | /fields/System.AreaPath |
| Iteration Path | /fields/System.IterationPath |
Operations: add (set/replace), replace (fails if missing), remove (clear)
HTML values must be on a single line (no embedded newlines).
Web link
https://devops.example.com/DefaultCollection/MyProject/_workitems/edit/$ARGUMENTS/
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

