免费在 GitHub 公开

feature-branch

Create a feature branch from an Azure DevOps ticket. Fetches ticket title, slugifies, creates `feature/<id>-<slug>`, and optionally transitions ticket to Active. Trigger when user says "feature branch", "create branch", "/dev-azdo:feature-branch", or provides a ticket id/URL to start work on.

中文简介正在准备中。当前显示原文说明。

lttr/claude-marketplace

集成工具Azure

查看安装方法

包含的文件（1）

SKILL.md2.5 KB

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

Feature Branch

Create feature/<ticket-id>-<slug> from an Azure DevOps work item.

Input Detection

Take the ticket from the request.

Form	Meaning
empty	look in recent context for ticket; else ask
numeric (`12345`)	ticket id, fetch title for slug
URL containing `_workitems/edit/<id>`	extract id, fetch title
`<id> <slug-override>`	use override slug, skip title fetch

Workflow

1. Resolve ticket + slug

empty

Scan recent conversation for work item id + title (e.g. prior triage output). Else ask user.

id / URL

az boards work-item show --id <id> --query '{id:id, title:fields."System.Title"}' -o json

Slugify title: lowercase, strip special chars, spaces→hyphens, 3–5 words max.

`<id> <override>`

Use override directly. Slugify same rules.

2. Pre-flight

git status --short

If dirty, warn and ask: stash or abort.

git branch --show-current

Resolve the default branch as described in ${CLAUDE_PLUGIN_ROOT}/references/conventions.md. The new branch starts from the current HEAD. If the current branch is not the default branch, name it and ask whether stacking the new branch on it is intended. On no, stop and let the user switch first. Skip the question when feature/<id>-<slug> already exists, since step 3 only switches to it.

3. Create branch

git checkout -b feature/<id>-<slug>

If branch already exists → switch to it instead, inform user.

4. Optional: transition ticket → Active

Prompt: "Transition ticket #<id> to Active? (y/N)"

Default: No.

If yes → invoke the ticket skill with state <id> active.

5. Confirm

Print created branch name + ticket transition status.

Notes

Branch and ticket transition are intentionally separate. feature-branch only offers the transition.
Later state changes are offered by dev-azdo:pr (Code Review after create, the next state after complete) and go through the ticket skill.

评价

还没有评价。欢迎分享你的使用感受。

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

同一仓库的技能

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.

中文简介正在准备中。当前显示原文说明。