Skip to content
cccskills
FreePublished on 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.

The English summary is being prepared. Showing the original description.

Works withAzure

Run score Not tested

See how to install

Files included (1)

  • SKILL.md2.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Feature Branch

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

Input Detection

Take the ticket from the request.

FormMeaning
emptylook 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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

The English summary is being prepared. Showing the original description.

lttr/claude-marketplace2Updated Oct 22, 2026

Use this skill when the user asks to test, verify, interact with, or automate web pages and browsers. Trigger for requests involving Chrome automation, browser testing, web scraping, screenshot capture, element selection, or checking web applications. Also trigger when user mentions "browser tools" explicitly.

The English summary is being prepared. Showing the original description.

lttr/claude-marketplace2Updated Oct 22, 2026

Show recent Claude Code changes personalized to user's setup. Trigger when user asks about changelog, "what's new", "cc changelog", "claude code updates", "recent changes", or wants to know what changed in Claude Code.

The English summary is being prepared. Showing the original description.

lttr/claude-marketplace2Updated Oct 22, 2026

Review code changes from current branch, an Azure DevOps PR, a git ref, or a diff/patch file. Trigger when user says "review this", "code review", "/df:code-review", or provides a PR id/URL, ticket URL, git ref, or diff path. Read-only — never posts comments.

The English summary is being prepared. Showing the original description.

lttr/claude-marketplace2Updated Oct 22, 2026

Review code changes from the current branch, staged changes, a git ref, or a diff/patch file. Pure git-native — no platform/PR awareness. Trigger when user says "review this", "review diff", "/aiwork:code-review-diff", or provides a git ref or diff path. Read-only — never posts comments.

The English summary is being prepared. Showing the original description.

lttr/claude-marketplace2Updated Oct 22, 2026

Czech typography rules for web development. Use when building web pages in Czech language, writing Czech content, or fixing typography issues in Czech text. Covers punctuation, dashes, quotes, numbers, units, non-breaking spaces, and HTML entities.

The English summary is being prepared. Showing the original description.

lttr/claude-marketplace2Updated Oct 22, 2026

See all skills by lttr

Report a problem with this skill