azure-devops-details
Retrieve complete details for specific Azure DevOps work items by ID, including all fields, comments, change history, and related items. Use when the user asks about a specific ticket number or needs full context on a work item. PAT token in .env file at network/.env.
When & Why to Use This Skill
This Claude skill provides a comprehensive integration for Azure DevOps, enabling users to retrieve exhaustive details for specific work items by ID. It streamlines project tracking by surfacing critical data including field values, full comment threads, revision history, and complex parent-child relationships, allowing for deep contextual understanding of tickets directly within the AI conversation.
Use Cases
- Instant Ticket Context: Quickly fetch the full description, priority, and acceptance criteria for a specific bug or user story using its ID.
- Communication Review: Retrieve and summarize all discussion comments on a work item to get up to speed on the latest team feedback and decisions.
- Audit and History Tracking: Examine the change history of a ticket to identify who modified specific fields and when the status was updated.
- Dependency Analysis: Use the 'ExpandRelations' feature to identify linked parent or child items, helping to map out project blockers and task hierarchies.
| name | azure-devops-details |
|---|---|
| description | Retrieve complete details for specific Azure DevOps work items by ID, including all fields, comments, change history, and related items. Use when the user asks about a specific ticket number or needs full context on a work item. PAT token in .env file at network/.env. |
Azure DevOps Work Item Details
Retrieve complete details for specific work items by ID, including all fields, comments, history, and related items.
Prerequisites Setup
Complete One-Liner Setup
Get-Content c:\Users\mshepherd\p\useful\network\.env | ForEach-Object { if ($_ -match '^(AZURE_DEVOPS_\w+)=(.+)$') { Set-Item "env:$($matches[1])" $matches[2] } }; Import-Module c:\Users\mshepherd\p\useful\network\AzureDevOpsTools\AzureDevOpsTools.psd1 -Force; Initialize-AzureDevOps -Organization $env:AZURE_DEVOPS_ORG -Project $env:AZURE_DEVOPS_PROJECT
Usage Examples
Get single work item
$item = Get-WorkItem -Ids 6673
Write-Host "[$($item.Id)] $($item.Title)"
Write-Host "State: $($item.State)"
Write-Host "Assigned To: $($item.AssignedTo)"
Write-Host "Description: $($item.Description)"
Get multiple work items
$items = Get-WorkItem -Ids 6673,6674,6675
$items | Format-Table Id, Title, State, AssignedTo -AutoSize
Get with relations (parent/child items)
$item = Get-WorkItem -Ids 6673 -ExpandRelations
# This will include related work items in the response
Get all comments
$comments = Get-WorkItemComments -Id 6673
Write-Host "Total comments: $($comments.Count)"
$comments | ForEach-Object {
Write-Host "[$($_.CreatedBy)] $($_.CreatedDate)"
Write-Host $_.Text
Write-Host ""
}
Get change history
$history = Get-WorkItemHistory -Id 6673
$history | Format-Table Rev, RevisedBy, RevisedDate, ChangedFields -AutoSize
Get related items
# Get all related items
$related = Get-RelatedWorkItems -Id 6673
Write-Host "Found $($related.Count) related items"
# Get only child items
$children = Get-RelatedWorkItems -Id 6673 -RelationType Child
# Get parent item
$parent = Get-RelatedWorkItems -Id 6673 -RelationType Parent
Available Functions
Get-WorkItem
Returns full work item details including all fields.
Parameters:
Ids- Work item IDs (single or comma-separated)ExpandRelations- Include related work items
Get-WorkItemComments
Returns all comments/discussions on the work item.
Parameters:
Id- Work item ID
Get-WorkItemHistory
Returns revision history showing who changed what and when.
Parameters:
Id- Work item ID
Get-RelatedWorkItems
Returns parent, child, or related work items.
Parameters:
Id- Work item IDRelationType- Parent, Child, Related, or All (default)
Output Format
Work items include:
Id- Work item IDType- Bug, User Story, Task, FeatureTitle- Work item titleState- Current stateAssignedTo- Assigned userDescription- Full descriptionAcceptanceCriteria- Acceptance criteriaPriority- Priority levelEffort- Effort estimateTags- TagsCreatedBy,CreatedDate- Creator infoChangedBy,ChangedDate- Last modified infoAreaPath,IterationPath- PathsUrl- Web URL for Azure DevOps- All custom fields
Comments include:
Text- Comment textCreatedBy- AuthorCreatedDate- When posted
Tips for AI Assistants
- Always load .env file first to get credentials
- Use this when user mentions a specific ticket number
- Get comments to understand discussion context
- Check history to see who worked on it and what changed
- Use ExpandRelations to see linked parent/child items
- Display results in a readable format
- Organization is "Legislative" and project is "LegBone"
Common Patterns
Pattern: Get ticket with full context
Get-Content c:\Users\mshepherd\p\useful\network\.env | ForEach-Object { if ($_ -match '^(AZURE_DEVOPS_\w+)=(.+)$') { Set-Item "env:$($matches[1])" $matches[2] } }; Import-Module c:\Users\mshepherd\p\useful\network\AzureDevOpsTools\AzureDevOpsTools.psd1 -Force; Initialize-AzureDevOps -Organization $env:AZURE_DEVOPS_ORG -Project $env:AZURE_DEVOPS_PROJECT; $item = Get-WorkItem -Ids 6673; Write-Host "[$($item.Id)] $($item.Title)"; Write-Host "State: $($item.State) | Assigned: $($item.AssignedTo)"; Write-Host "Link: https://dev.azure.com/$env:AZURE_DEVOPS_ORG/$env:AZURE_DEVOPS_PROJECT/_workitems/edit/$($item.Id)"
Pattern: Get ticket with comments
$item = Get-WorkItem -Ids 6673
$comments = Get-WorkItemComments -Id 6673
Write-Host "Work Item: [$($item.Id)] $($item.Title)"
Write-Host "`nComments ($($comments.Count)):"
$comments | ForEach-Object { Write-Host "- [$($_.CreatedBy)] $($_.Text)" }