pharoslisted

Use for AZURE DEVOPS work — when the user says Azure DevOps, ADO or dev.azure.com, or names an ADO work item by number ("pick up 4821"). Covers reading or updating a work item, bug, story or epic; the board, backlog, sprint or iteration; what is assigned to you; reading or writing a wiki page and its comments; searching the board and wiki for a phrase; linking a plan to an epic; attaching a file to a work item or taking one off; inline images in a field or page; @mentioning somebody so they are notified; importing Markdown, Word or PDF as pages; and whether a call is retryable. ALSO the GITHUB ISSUE ↔ work item EDGE: adopting an issue as a work item linked at both ends, bulk-adopting a repo, one reply reaching both, where they drifted, closing both ends together, and changing a comment that ALREADY EXISTS: editing, deleting, reacting, hiding, pinning. NOT a GitHub CLI: listing or viewing an issue, or POSTING a comment, is `gh`'s job. NOT for other trackers — Argus, Jira, Linear.
ASNNetworks/floh-skills · ★ 0 · Data & Documents · score 75

Install: claude install-skill ASNNetworks/floh-skills

# Working Azure DevOps with `pharos` `pharos` is a CLI that gives you Azure DevOps from a shell, authenticated by an environment variable rather than a browser login. **Everything it can do is listed below. Do not run `pharos --help` to find out** — that costs several calls and this section is the same information. ``` whoami who ADO_PAT belongs to. @Me resolves to this types what --state and --type will ACCEPT, per type query WHICH work items — assigned to you, in a sprint, of a type, still open. Hydrated items, not ids. search <terms...> WHERE something is WRITTEN — full text across work items AND wiki pages, in one call. Reaches descriptions, discussion and page bodies, which `query` cannot. Each result carries the MATCHING LINE. --items / --wiki to narrow, --org for the whole organisation, --top (default 25) task <id> one work item, whole: fields, comments, attachments, relations WITH titles, and the content + discussion of every linked wiki page --children an EPIC and everything under it, in ONE call. --depth <n> for deeper (max 5)