azure-devops
/azure-devops
Interact with Azure DevOps repositories, pull requests, and APIs using the AZURE_DEVOPS_TOKEN environment variable. Use when working with code hosted on Azure DevOps or managing Azure DevOps resources.
- Author
- OpenHands ↗
- Repository
- extensions ↗
- Licence
- MIT
- Last repository change
- 25.10.2026
Assessment and security
- Files in this package
- 5
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 8
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Interact with Azure DevOps repositories, pull requests, and APIs using the AZURE_DEVOPS_TOKEN environment variable. Use when working with code hosted on Azure DevOps or managing Azure DevOps resources.
Original author description
Interact with Azure DevOps repositories, pull requests, and APIs using the AZURE_DEVOPS_TOKEN environment variable. Use when working with code hosted on Azure DevOps or managing Azure DevOps resources.
How it works
- Connection selection
- Git
- Azure DevOps API Usage
SKILL.md preview
---
name: azure-devops
description: Interact with Azure DevOps repositories, pull requests, and APIs using the AZURE_DEVOPS_TOKEN environment variable. Use when working with code hosted on Azure DevOps or managing Azure DevOps resources.
triggers:
- azure_devops
- azure
---
## Connection selection
Use authenticated Azure DevOps MCP tools first when they are available in the agent's environment. Detect this by tool availability, without depending on a particular MCP server name. Use the token and direct API instructions below only when Azure DevOps MCP tools are unavailable or when raw API or `curl` access is explicitly needed.
You have access to an environment variable, `AZURE_DEVOPS_TOKEN`, which allows you to interact with
the Azure DevOps API.
<IMPORTANT>
You can use `curl` with the `AZURE_DEVOPS_TOKEN` to interact with Azure DevOps's API.
ALWAYS use the Azure DevOps API for operations instead of a web browser.
</IMPORTANT>
## Git
Use plain `git clone`, `git fetch`, `git pull` and `git push`. OpenHands sets up git credentials for each Azure DevOps organization the user belongs to, so these commands work for any repository in those organizations, not only the one that was opened. Run them with `GIT_TERMINAL_PROMPT=0` so git fails at once instead of waiting at a username or password prompt.
A repository written as `ORG/PROJECT/REPO` is cloned from `https://dev.azure.com/ORG/PROJECT/_git/REPO`:
```bash
GIT_TERMINAL_PROMPT=0 git clone https://dev.azure.com/ORG/PROJECT/_git/REPO
```
Do not put `AZURE_DEVOPS_TOKEN` in a remote URL or pass it to git as an option: a token saved in `.git/config` stays on disk and stops working when it expires. If git fails because it needs a username or password, credentials are not set up for that organization; tell the user instead of embedding the token.
Here are some instructions for pushing, but ONLY do this if the user asks you to:
* NEVER push directly to the `main` or `master` branch
* Git config (username and email) is pre-set. Do not modify.
* You may already be on a branch starting with `openhands-workspace`. Create a new branch with a better name before pushing.
* Once you've created your own branch or a pull request, continue to update it. Do NOT create a new one unless you are explicitly asked to. Update the PR title and description as necessary, but don't change the branch name.
* Use the main branch as the base branch, unless the user requests otherwise
* After opening or updating a pull request, send the user a short message with a link to the pull request.
* Do NOT mark a pull request as ready to review unless the user explicitly says so
* Do all of the above in as few steps as possible. E.g. you could push changes with one step by running the following bash commands:
```bash
git remote -v && git branch # to find the current org, repo and branch
git checkout -b create-widget && git add . && git commit -m "Create widget" && GIT_TERMINAL_PROMPT=0 git push -u origin create-widget
```
On Windows PowerShell, set `$env:GIT_TERMINAL_PROMPT = "0"` and run those `git` commands as separate commands if `&&` is not supported by the installed shell.
## Azure DevOps API Usage
`AZURE_DEVOPS_TOKEN` is either a Personal Access Token (PAT) or, for users who sign in with Microsoft Entra ID, an Entra access token. Basic authentication works with both: leave the username empty and use the token as the password. An Entra access token can also be sent as `Authorization: Bearer $AZURE_DEVOPS_TOKEN`.
Here's how to authenticate with curl:
```bash
# Base64-encode ":<token>" on one line (Entra tokens are long enough to wrap)
AUTH=$(echo -n ":$AZURE_DEVOPS_TOKEN" | base64 | tr -d '\n')
# Make API call
curl -H "Authorization: Basic $AUTH" -H "Content-Type: application/json" https://dev.azure.com/{organization}/{project}/_apis/git/repositories?api-version=7.1
```
PowerShell equivalent for the Basic header:
```powershell
$auth = [Convert]::ToBase64String([Text.Encoding]::ASCII.GetBytes(":$env:AZURE_DEVOPS_TOKEN"))
Invoke-RestMethod `
-Headers @{ Authorization = "Basic $auth"; "Content-Type" = "application/json" } `
-Uri "https://dev.azure.com/{organization}/{project}/_apis/git/repositories?api-version=7.1"
```
Common API endpoints:
- List repositories: `https://dev.azure.com/{organization}/{project}/_apis/git/repositories?api-version=7.1`
- Get repository details: `https://dev.azure.com/{organization}/{project}/_apis/git/repositories/{repositoryId}?api-version=7.1`
- List pull requests: `https://dev.azure.com/{organization}/{project}/_apis/git/pullrequests?api-version=7.1`
- Create pull request: `https://dev.azure.com/{organization}/{project}/_apis/git/repositories/{repositoryId}/pullrequests?api-version=7.1` (POST)
Files in this package (5)
- .claude-plugin 1 KB
- .codex-plugin 1 KB
- README.md 4 KB
- SKILL.md 5 KB
- .plugin/plugin.json 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · OpenHands/extensions | 100 | MIT |
| apideck-libraries/api-skills | 100 | Apache-2.0 |
| sanjay3290/ai-skills | 100 | Apache-2.0 |
| HelixDevelopment/agent | 100 | MIT |
| BagelHole/DevOps-Security-Agent-Skills | 100 | MIT |
| atc-net/atc-agentic-toolkit | 95 | MIT |
| MicrosoftDocs/Agent-Skills | 95 | CC-BY-4.0 |
| tuannv14/claude-team-toolkit | 90 | MIT |
Database snapshot: 13.11.2026 · package version c224c54140b5 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100azure-devops-workflow
Use Azure DevOps Services to triage Azure Boards work items or sprint backlogs, inspect and review Azure Repos pull requests, or diagnose Azure Pipelines builds and runs. Also use when the user supplies a dev.azure.com link for one of those resources. - 100azure-devops-rest-api
Guide for working with Azure DevOps REST APIs and OpenAPI specifications. Use this skill when implementing new Azure DevOps API integrations, exploring API capabilities, understanding request/response formats, or referencing the official OpenAPI specifications from the… - 100azure-devops-pipelines
Best practices for Azure DevOps Pipeline YAML files Triggers on: **/azure-pipelines.yml, **/azure-pipelines*.yml, **/*.pipeline.yml - 100devops
Use when unsure whether a request is a GitHub or Azure DevOps operation, or when someone says "devops help", "connect to devops", "check my work items or PRs", "devops?". Routes to devops-github or devops-azure based on intent. Also use as a fallback when a request doesn't clearly map to either one. - 100github
Interact with GitHub repositories, pull requests, issues, and workflows using the GITHUB_TOKEN environment variable and GitHub CLI. Use when working with code hosted on GitHub or managing GitHub resources. - 92github
Interact with GitHub repositories, pull requests, issues, and workflows using the GITHUB_TOKEN environment variable and GitHub CLI. Use when working with code hosted on GitHub or managing GitHub resources.