Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

ticket

Transition Azure DevOps work item state. Trigger when user says "ticket <id> active", "set ticket cr", "/df:ticket", or wants to move a work item between states (active, code-review, ready, closed).

In Manus ausführen

Überblick

Transition Azure DevOps work item state. Trigger when user says "ticket <id> active", "set ticket cr", "/df:ticket", or wants to move a work item between states (active, code-review, ready, closed).

Installationsbefehl

npx skills add https://github.com/lttr/claude-marketplace --skill ticket

Kopieren Sie diesen Befehl und fügen Sie ihn in Claude Code ein, um den Skill zu installieren

Quelle

lttr/claude-marketplace

Sterne2

Forks1

Aktualisiert18. Mai 2026 um 07:05

SKILL.md

readonly

name	ticket
description	Transition Azure DevOps work item state. Trigger when user says "ticket <id> active", "set ticket cr", "/df:ticket", or wants to move a work item between states (active, code-review, ready, closed).

Ticket

Update Azure DevOps work item state via az boards work-item update.

Input Format

$ARGUMENTS = <id> <state>.

Synonym	Azure DevOps state
`active`, `start`, `in-progress`	`Active`
`cr`, `code-review`, `review`	`Code Review`
`ready`, `done-dev`	`Ready`
`closed`, `done`, `complete`	`Closed`

Unknown state → ask user. Missing id → ask. Missing state → ask.

Workflow

1. Parse + map state

Extract id (numeric) and state synonym. Map to canonical Azure DevOps state.

2. Update

az boards work-item update --id <id> --state "<State>"

3. Confirm

Print: work item id, title, new state.

Notes

States above match the most common Azure DevOps process templates. If your project uses different state names (e.g. Doing, In Review), pass the exact label.
Branch creation lives in the feature-branch skill — keeps state changes orthogonal.

Mehr aus diesem Repository

gleiches Repository

code-review

lttr/claude-marketplace

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", "code review", "/df:code-review", or provides a git ref or diff path. Read-only — never posts comments.

2026-05-212

code-review

lttr/claude-marketplace

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.

2026-05-212

feature-branch

lttr/claude-marketplace

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", "/df:feature-branch", or provides a ticket id/URL to start work on.

2026-05-182

lttr/claude-marketplace

Manage Azure DevOps pull requests — create, checkout, list, complete. Trigger when user says "/df:pr <op>", "create PR", "checkout PR 123", "list PRs", "complete PR", or otherwise asks to operate on an AZDO pull request.

2026-05-182

skill-creator

lttr/claude-marketplace

Guide for creating and editing Claude Code skills. Use when user wants to create a new skill, create a new slash command (skills are the unified primitive - commands live in skills/ now), update an existing skill, or needs help structuring a SKILL.md file.

2026-05-172

cc-handoff

lttr/claude-marketplace

Write ~/.claude/custom-handoff.md to hand off current work to the next session

2026-05-152

Quelle

lttr

lttr/claude-marketplace

GitHub-Repository öffnen Creator-Repositorys ansehen

Installationsbefehl

Download

In Manus ausführen

Nützlich fürSOC

SoftwareentwicklerInformatik- und Mathematikberufe15-1252L4

name	ticket
description	Transition Azure DevOps work item state. Trigger when user says "ticket <id> active", "set ticket cr", "/df:ticket", or wants to move a work item between states (active, code-review, ready, closed).

Ticket

Update Azure DevOps work item state via az boards work-item update.

Input Format

$ARGUMENTS = <id> <state>.

Synonym	Azure DevOps state
`active`, `start`, `in-progress`	`Active`
`cr`, `code-review`, `review`	`Code Review`
`ready`, `done-dev`	`Ready`
`closed`, `done`, `complete`	`Closed`

Unknown state → ask user. Missing id → ask. Missing state → ask.

Workflow

1. Parse + map state

Extract id (numeric) and state synonym. Map to canonical Azure DevOps state.

2. Update

az boards work-item update --id <id> --state "<State>"

3. Confirm

Print: work item id, title, new state.

Notes

States above match the most common Azure DevOps process templates. If your project uses different state names (e.g. Doing, In Review), pass the exact label.
Branch creation lives in the feature-branch skill — keeps state changes orthogonal.