Azure DevOps PRs and work items via the `ado` CLI. Trigger: PR review/vote/comment, list/create/update work items.
Load when the task touches Azure DevOps: pull requests (review, vote, comment,
diff, create, chain), work items (list, get, update, create), or profiles. Use
the ado CLI — do NOT load the OpenCode plugin tools for these operations.
ado CLI (ado <group> <sub>). One command per action.vote, comment, update, create, chain.--type "User Story"; assignee resolved at runtime from ado wi list (@<name> column) — never hardcode; ALWAYS ask Social vs Infra Kanban first (Social → --profile ysocial --area "ySocial\Kanban"; Infra → --area "Infra\\Infra Kanban"); always ask Producto + Sponsors and pass --field Custom.USProducto=<v> and --field Custom.Sponsors=<v> (the template rejects the create without them); never --field System.AreaPath; --description is Azure DevOps HTML, and work item comments render as HTML too — wrap Markdown content in <pre> (see references/templates.md).[repo] is optional; omit it to auto-discover a PR by ID. --profile <name> overrides the active profile.| Need | Command group |
|---|---|
| Configure / not yet set up / "no profile" or auth error | ado init, ado config, ado show → see references/setup.md |
| Enable/disable or restrict work item creation | edit [work_item.create] in .adoconfig.toml → see references/setup.md |
| Which profile / switch it | ado profile · ado profile use <name> |
| Inspect a PR | ado pr get/context/threads/diff/file |
| Act on a PR | ado pr vote/comment/create/chain |
| Inspect a work item | ado wi get/list/related/types |
| Act on a work item | ado wi update/comment/create/create-child |
ado profile (and ado profile use if the wrong one is active).ado pr context <prId> or ado wi get <id>.--comment/--state/etc. as flags.references/commands.md — full command list, flags, examples, error handling.references/workflows.md — task playbooks: code review a PR, create/update
work items, create a PR or chain, find pending work.references/templates.md — work item body templates per type, and the
formatting rules: fields and comments are HTML; Markdown survives only inside
<pre>. Read before drafting one.references/setup.md — install, ado init, profiles/PAT, and .adoconfig.toml
rules (including whether ado wi create is enabled, allowed types, required fields).Setup-related requests ("configure ado", "set up the CLI", "no profile / auth
failing", "allow/disallow creating work items"): read references/setup.md first.
YoizenSA/dev-ai-workflow
36f5af5
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.