devops-workitem-read
Skill0 starsChanged 3 months agoMITView on GitHub
Fetch Azure DevOps work item details (title, state, description, acceptance criteria)
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-updateSkill
- 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
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 49
If the work item doesn't exist or access is denied, report the error clearly.
≈ “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
Read Azure DevOps Work Item
Work item ID: $ARGUMENTS
Your task
Fetch the work item details from Azure DevOps using the REST API with integrated Windows authentication.
Execute
curl -L --negotiate -u : "https://devops.example.com/DefaultCollection/MyProject/_apis/wit/workitems/$ARGUMENTS?api-version=6.0"Parse and display
Extract and display the following fields from the JSON response:
| Field | JSON Path |
| ID | id |
| Title | fields.System.Title |
| Type | fields.System.WorkItemType |
| State | fields.System.State |
| Assigned To | fields.System.AssignedTo.displayName |
| Description | fields.System.Description |
| Acceptance Criteria | fields.Microsoft.VSTS.Common.AcceptanceCriteria |
| Sprint | fields.System.IterationPath |
| Area | fields.System.AreaPath |
Output format
Present a clean summary with:
- Work item ID and title
- Current state and assignee
- Description (strip HTML tags for readability)
- Acceptance criteria (if present)
- Link to web UI:
https://devops.example.com/DefaultCollection/MyProject/_workitems/edit/$ARGUMENTS/
Error handling
If the work item doesn't exist or access is denied, report the error clearly.
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.