菜单
Deeply gather context from an Azure DevOps work item by following its relations, linked PRs, hyperlinks, and comments. Use whenever a command needs the full picture behind a work item -- planning features, reviewing PRs, triaging, or estimating.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Common steps for creating a new Azure DevOps work item in the FundGuard project, including iteration assignment, parent linking, and triage. Called by create-task, create-bug, and request-environment-access skills — not invoked directly by the user.
Mechanical estimate-and-transition of an Azure DevOps work item to the Triaged state. Called programmatically by skills that create or triage work items -- not invoked directly by the user. For user-initiated triage, use the triage skill instead.
Transitions an Azure DevOps work item to the Active state. Use when starting work on a work item, given an explicit ID or one inferred from the current feature branch.
Marks an Azure DevOps work item as Blocked and links it to its predecessor blocker. Use when a work item cannot proceed until another work item is completed.
Investigates bugs to find root cause, designs a TDD-based fix plan, and implements after approval. Use when given a bug ticket or description of defective behaviour that needs investigation and fixing in the codebase.
Follows up on a previous /review-pr or /review-plan review to check whether findings were addressed. Use in the same conversation as a preceding review invocation.
| name | work-item-context |
| description | Deeply gather context from an Azure DevOps work item by following its relations, linked PRs, hyperlinks, and comments. Use whenever a command needs the full picture behind a work item -- planning features, reviewing PRs, triaging, or estimating. |
Given a work item ID, build a rich understanding of the item by fetching the item itself and following its linked artefacts. Return a structured summary that the calling command can use as authoritative context.
Call get_work_item with expand: "relations" to retrieve fields, relations, and linked resources in a single call.
Extract the core fields: title, type, state, description, acceptance criteria, repro steps (if present), assigned-to, iteration, and area path.
Extract IDs from the relations array, grouped by link type:
Batch-fetch all linked work items via batch_search_workitems (up to 15 parallel searches in one call). For each, note its ID, title, type, and state.
Limit traversal to one hop -- do not recurse into the linked items' own relations.
Extract pull-request links from the relations array (vstfs:///Git/PullRequestId/...). Fetch each via get_pr_details and note the PR ID, title, status, source branch, and target branch.
Scan the description, acceptance criteria, and repro-steps fields for URLs. Categorise and fetch:
| URL pattern | Action |
|---|---|
| ADO wiki link | Fetch via wiki_get_page_content |
| Other HTTP(S) URL | Fetch via WebFetch (best-effort; skip on failure) |
Skip URLs that clearly point to images, videos, or binary assets.
Comments are already included in the get_work_item response from step 1 (includeComments defaults to true). Incorporate any decisions, clarifications, or additional context from the comments.
Produce a structured summary for the calling command:
## Work Item Context: #<ID> -- <Title>
**Type**: <type> | **State**: <state> | **Iteration**: <iteration>
### Goal
<Restated goal from description and acceptance criteria>
### Acceptance Criteria
<Bullet list, verbatim or lightly reformatted>
### Key Decisions (from comments)
<Bullet list of decisions, clarifications, or scope changes>
### Related Work Items
| ID | Title | Type | State | Relation |
|----|-------|------|-------|----------|
### Linked PRs
| ID | Title | Status | Branch |
|----|-------|--------|--------|
### Supplementary Material
<Summaries of fetched hyperlinks and wiki pages>
Omit any section that has no content rather than showing an empty table.