無料GitHub で公開

ticket

Creating an Azure DevOps work item or posting a comment with the obvious `az boards` command silently stores HTML that cannot be fixed afterward. Use this instead. Also covers reading a work item and transitioning its state. Trigger on "create ticket", "new work item", "comment on

lttr/claude-marketplace

インストール方法を見る

含まれるファイル（5）

SKILL.md2.2 KB
references/comment.md5.2 KB
references/create.md8.5 KB
references/show.md2.5 KB
references/state.md2.7 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Ticket (Azure DevOps work item)

Multi-op skill. Pick the op from the intent of the request, read its reference, run the steps, report the result.

Shared rules (org/project resolution, approval gate, writing, request bodies) live in ${CLAUDE_PLUGIN_ROOT}/references/conventions.md. Read it before the first op.

Dispatch

Op	Input	Reference
show	work item id	`${CLAUDE_SKILL_DIR}/references/show.md`
create	what the item is about, optionally its type, parent, tags, and a description or a file with one	`${CLAUDE_SKILL_DIR}/references/create.md`
comment	work item id and the comment text or a file with it, or which comment to update or delete	`${CLAUDE_SKILL_DIR}/references/comment.md`
state	work item id and the target state, or none to get the next state proposed	`${CLAUDE_SKILL_DIR}/references/state.md`

Ambiguous intent, or an op with no id where one is required: ask. An id plus a state name with no other intent means state.

create and comment write to a shared board under the user's name. Both go through the approval gate. Do not skip it.

Notes

Branch creation lives in dev-azdo:feature-branch, which offers ticket state <id> active after branching.
dev-azdo:pr offers state <id> cr after creating a PR and the next state after completing one.
Pull-request threads are a different API. Use dev-azdo:pr (comments op).

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

aiwork-protocol

無料

Structure AI work artifacts under .aiwork/{YYYY-MM-DD}_{slug}/ folders using the project's protocol (intent, triage, research, spec, prd, areas, plan, review, notes, docs/). Use when the user asks to plan, capture an intent, make a spec, triage, research a task, write a report, code review, summarize findings, save the work, document decisions, record this, write that down, persist findings, or references any path under .aiwork/. Also use when starting a non-trivial task that needs a plan or spec before implementation, or when finishing one and capturing notes.

日本語の概要は準備中です。原文の説明を表示しています。