scaryrawr/ado-cli

Azure DevOps Router

Use this skill when a user gives you an Azure DevOps URL or needs the shared attachment-upload helper.

Script execution model

• Run the bundled helpers via the skill-relative paths shown below (./scripts/... resolves from this skill directory).
• The helper scripts are non-interactive. Read structured JSON from stdout and treat stderr as diagnostics.
• If you need to confirm flags or subcommands, run ./scripts/ado-cli.mts --help.

Available scripts

parse-url

Always normalize the URL with the script instead of manually re-parsing host and path segments:

./scripts/ado-cli.mts parse-url "https://dev.azure.com/{org}/{project}/_git/{repo}/pullrequest/{prId}"

The script returns structured JSON including:

• organization
• organizationUrl
• project
• repository when present
• resourceType
• resourceId
• routeSkill

Routing rules:

• pull-request -> ado-pr
• work-item -> ado-work-items
• unknown -> inspect the user request and choose make-pr, review-pr, or another flow yourself

upload-attachment

When you need a PR attachment URL, use the script instead of rebuilding the token + binary upload flow inline:

./scripts/ado-cli.mts upload-attachment \
  --org {org-or-url} \
  --project {project} \
  --repository-id {repositoryId} \
  --pull-request-id {prId} \
  --file /absolute/path/to/image.png

The script returns fileName, filePath, id, and url as JSON.

Workflow

1. Parse the Azure DevOps URL with parse-url.
2. Use routeSkill for existing resource URLs. If the parse result is unknown, choose make-pr or review-pr from the user's request instead of expecting the parser to infer intent.
3. Reuse organizationUrl or the parsed project/repository identifiers when later Azure CLI commands need explicit scope.
4. Use upload-attachment only when the task needs a PR attachment URL.

Organization detection

For Azure CLI commands that support it, prefer --detect true when you are inside the target repository.

If auto-detection fails, fall back to organizationUrl from the parse result or a user-supplied org URL.

Rules

• Prefer the script output over handwritten URL parsing.
• Prefer the script output over handwritten curl + python3 attachment upload snippets.
• Fail loudly when the URL host or path is unsupported.