Look up Azure DevOps, VSTS, and Jira work items by ID or keywords.
npx skills add https://github.com/TomazWang/agent-toolkit --skill vsts-lookup
Please help me install this Agent Skill. Skill: vsts-lookup Source: https://github.com/TomazWang/agent-toolkit/tree/main/plugins/kb-analysis/skills/vsts-lookup Command: npx skills add https://github.com/TomazWang/agent-toolkit --skill vsts-lookup
Allows developers to attach rationale to code changes by retrieving context from VSTS/Azure DevOps and Jira tickets.
Provide a ticket ID or keywords to retrieve and summarize the ticket context.
High-intent search queries and answers about installing and using this skill.
Trace code change rationale by looking up related Azure DevOps or Jira tickets using a direct ID or keyword search. The tool extracts structured ticket details like title, status, and discussion sections into a concise report to reveal the decision context.
Yes, you can retrieve ticket context from both VSTS and Jira. The lookup tool applies across Azure DevOps, VSTS, and Jira, allowing you to inspect related commits, PRs, and defect tickets to understand the rationale behind code decisions.
Searching for work items by keyword extracts structured ticket details including title, type, status, resolution, and dates. It also pulls rationale sections such as the problem, solution, and discussion to provide concise context for code changes.
Find the rationale behind a pull request by performing a direct ticket lookup using the defect ticket ID. The tool retrieves the associated work item and presents the problem, solution, and discussion fields as a concise contextual report.
Yes, it works for tracing commits across Azure DevOps by using keyword search to discover related work items. You can locate tickets associated with code changes even when explicit ticket IDs are not directly linked in the commit messages.
The best way to record ticket context is to save the extracted work item details into topic notes. After looking up a ticket by ID or keyword, the tool allows you to record the structured findings for later reference during code analysis.
jpcaparasGenerate local Azure DevOps work item packets from repository context.
whmathews15Document major decisions with context, rationale, and follow-up actions.
skyosevAudit TypeScript code for missing inline explanations of non-obvious decisions.
zbyCreate, list, update, and complete tickets in Markdown files with YAML frontmatter.
