Git DevOps Assistant (MCP Powered)

Stop context-switching. Start shipping. Your AI-powered Azure DevOps and GitHub companion lives right inside VS Code — talk to your boards, pipelines, repos, pull requests, issues, wikis, and GitHub Actions in plain English through GitHub Copilot.

Install → Sign in → Type @devops → Done. No config files, no API tokens, no YAML to write. The built-in ADO MCP server connects to your Azure DevOps org automatically, and an optional GitHub MCP server lights up the moment you tell the assistant your code lives on GitHub.com or GitHub Enterprise.

Work items always live in Azure DevOps. Code can live in Azure DevOps repos or GitHub. On first run the assistant asks “Where does your code live?” — pick Azure DevOps, GitHub.com, or GitHub Enterprise, and every code command (/code, /draftpr, /createpr, /myactivity) automatically targets the right host. See Azure DevOps + GitHub.

ℹ️ Important Notice

This extension is built by Microsoft Digital as an engineering-productivity tool that uses an ADO MCP server and an optional GitHub MCP server, provides AI-powered skills, and offers prebuilt prompts to streamline Azure DevOps and GitHub workflows. It is an official Microsoft Digital extension, but it is not a supported product offering from the Azure DevOps or GitHub product teams.

GitHub Copilot and Azure DevOps are trademarks of their respective owners. This extension enhances the Azure DevOps experience through AI-powered assistance.

For Support & Feedback: Please use the VS Code Marketplace Q&A section for any questions, feedback, bug reports, or feature requests. Your input helps us improve the extension.

🎬 Get Set Up in Under 2 Minutes

Before you can use any of the features below, complete these steps:

Install the extension from the VS Code Marketplace
Sign in to Azure DevOps when prompted
Configure your organization and project (see Getting Started for details)
Choose where your code lives — on first run the assistant asks “Where does your code live?”: pick Azure DevOps, GitHub.com, or GitHub Enterprise. Picking a GitHub option signs you in and enables repo/PR/issue/Actions tools (see Azure DevOps + GitHub). Re-run anytime with "Git DevOps Assistant: Set up GitHub integration".

Once you're signed in and configured, open Copilot Chat and try any of these:

What you want	Just type this
"Am I ready to ship?"	`/ado-release-manager are we ready to release?`
"How's the sprint going?"	`@devops /sprint`
"Review my ADO PR"	`/ado-pr-reviewer review PR #12345`
"Review my GitHub PR"	`/github-pr-reviewer review owner/repo#123`
"Triage my GitHub issues"	`/github-issue-triage triage issues in owner/repo`
"Why did my Action fail?"	`/github-actions-investigator why did my build fail?`
"Where's the tech debt?"	`/ado-tech-debt-analyzer tech debt report`
"I'm new — help me ramp up"	`/ado-project-onboarding I'm new to this project`
Draft a PR description	`@devops /draftpr 123456`
Create a PR from current branch	`@devops /createpr`
Verify my code meets requirements	`@devops /reqcheck 123456`
Check build/pipeline status	`@devops /build`
Update a work item inline	`@devops /update 123456 state=Active`
See what I've been up to	`@devops /myactivity`
Any question in plain English	`@devops What PRs need my review?`

Two ways to interact — use both. Slash commands like @devops /draftpr and /ado-scrum-master give you fast, repeatable shortcuts for specific tasks. For everything else, just type @devops followed by any question in plain English — @devops show me failed builds today, @devops what bugs are assigned to me? — and the MCP tools handle the rest.

In Agent Mode, you don't even need the @devops tag — just ask and the tools activate automatically.

Keep reading to explore all 9 AI Skills (5 for Azure DevOps, 4 for GitHub), the built-in ADO + GitHub MCP servers, and 17 slash commands — there's a lot more to discover.

🔄 How It Works — End-to-End

This section walks through exactly what happens from install to your first answer, and how the assistant decides whether to talk to Azure DevOps, GitHub.com, or GitHub Enterprise.

First-Run Setup Flow

Do I have to pick a tenant when I sign in? No. Sign-in uses your default Microsoft account silently — if you're already signed in to VS Code, there's no prompt at all. You only set a tenant later (one optional setting) if you're a guest in another company's Azure DevOps tenant. See Guest / Multi-Tenant.

  Install extension
        │
        ▼
  Extension activates
        │
        ▼
  Silent Microsoft sign-in  ──  uses your DEFAULT account/tenant
        │
        ▼
  ADO org & project saved? ──No──▶ Prompt: Organization name or URL
        │                                  │
       Yes                                 ▼
        │                          URL included a project?
        │                          ├─ Yes ─▶ save org + project
        │                          └─ No ──▶ Prompt: Project name ─▶ save
        ▼                                  │
  Create ADO client + start Azure DevOps MCP server  ◀───────────┘
        │
        ▼
  First run? ──No──▶ Ready ✅
        │
       Yes
        │
        ▼
  "Where does your code live?"  (GitHub.com / Enterprise / ADO-only)
        │
        ▼
  Sign in to chosen host + start GitHub MCP server
        │
        ▼
  Ready ✅ — use @devops in chat

Where your code lives — ADO vs GitHub vs GitHub Enterprise

The extension runs two independent MCP servers. Which one answers a request depends on your GitHub setting and the current workspace's git remote — an explicit host choice always wins, but a *.ghe.com repo is auto-detected even if your setting still says github.com.

  Your @devops question
          │
          ▼
  GitHub integration enabled?
   ├─ No ──▶ Azure DevOps MCP only  (scoped to your org + project)
   │
   └─ Yes ─▶ Azure DevOps + GitHub MCP tools
                     │
                     ▼
              Which GitHub host?
               ├─ github.com ─────────────▶ Hosted Copilot MCP endpoint
               ├─ *.ghe.com (Ent. Cloud) ─▶ Your tenant's hosted endpoint
               └─ Ent. Server (self-host) ▶ Your custom mcpServerUrl

Target	When it's used	Setup needed
Azure DevOps	Always — work items, repos, pipelines, wiki, tests	Org + project (step 2–3)
GitHub.com	`github.com` host selected / detected	GitHub sign-in
GitHub Enterprise Cloud (`*.ghe.com`)	Enterprise host on a data-residency domain	GitHub sign-in + base URL
GitHub Enterprise Server (self-hosted)	Enterprise host with no hosted MCP endpoint	Base URL and `adoProductivity.github.mcpServerUrl`

🧠 9 AI Skills — Your Team's Superpowers

Skills are ready-to-use AI experts that ship with this extension. Each one chains multiple Azure DevOps or GitHub API calls behind a single conversational prompt — no scripting, no queries, no dashboards to build. They auto-install when you install the extension.

5 skills target Azure DevOps (/ado-*) and 4 target GitHub (/github-*). The GitHub skills work on github.com and GitHub Enterprise Cloud (*.ghe.com) and operate against the single host you configured — they never ask "Azure DevOps or GitHub?".

🏃 Scrum Master — `/ado-scrum-master`

"Show me the sprint, not the spreadsheet."

Your AI Scrum Master pulls live data from Azure DevOps and delivers ceremony-ready insights in seconds.

Try this	What you get
`/ado-scrum-master How's our sprint?`	Sprint progress %, at-risk items, blockers, capacity utilization
`/ado-scrum-master standup summary`	Per-member status: done, in-progress, blocked — with work item IDs
`/ado-scrum-master plan next sprint`	Capacity-aware recommendations from your prioritized backlog
`/ado-scrum-master run a retro`	Delivered vs. planned, patterns, and generated action items
`/ado-scrum-master backlog refinement`	Flags missing criteria, oversized stories, duplicates, priority gaps

🔍 PR Reviewer — `/ado-pr-reviewer`

"Review this PR like a Staff Engineer would."

Analyzes real diffs, existing comments, linked work items, and build status — then delivers a structured, severity-rated review.

Try this	What you get
`/ado-pr-reviewer review PR #12345`	Full review: 🔴 Critical / 🟡 Important / 🔵 Suggestions with file & line refs
`/ado-pr-reviewer security review PR #12345`	Hardcoded secrets, injection risks, auth gaps, input validation issues
`/ado-pr-reviewer check test coverage for PR #12345`	Changed files mapped to test files — highlights what's missing

🚀 Release Manager — `/ado-release-manager`

"Are we ready to release? Give me the receipts."

Pre-release checklist backed by live build, test, PR, and security data.

Try this	What you get
`/ado-release-manager are we ready to release?`	✅/❌ checklist: builds, open PRs, bugs, test results, security alerts
`/ado-release-manager why did build #456 fail?`	Root cause from build logs, failing tests, and the commit that broke it
`/ado-release-manager pipeline dashboard`	All pipelines with success rates and failure diagnostics
`/ado-release-manager generate release notes`	Auto-generated notes from commits and linked work items

🏥 Tech Debt Analyzer — `/ado-tech-debt-analyzer`

"How healthy is this codebase, really?"

Data-driven health scores across bugs, PRs, builds, and security — with sprint-allocation recommendations.

Try this	What you get
`/ado-tech-debt-analyzer tech debt report`	🟢/🟡/🔴 scores for bugs, stale PRs, build stability, security, untriaged items
`/ado-tech-debt-analyzer aging bugs`	Bugs sorted by age, severity, assigned-to, and days since last update
`/ado-tech-debt-analyzer stale PRs`	PRs open too long, unresolved comments, recommended action per PR
`/ado-tech-debt-analyzer backlog hygiene`	Items missing acceptance criteria, assignments, or area paths

🎯 Project Onboarding — `/ado-project-onboarding`

"I just joined. Catch me up — from the real data."

Generates a personalized onboarding summary from your live Azure DevOps project — teams, sprints, repos, pipelines, wikis, and current work.

Try this	What you get
`/ado-project-onboarding I'm new to this project`	Full onboard: teams, sprint cadence, repos, pipelines, wiki links, current sprint work
`/ado-project-onboarding who's on the team?`	Team roster with current work assignments
`/ado-project-onboarding what repos do we have?`	Repo listing with branch strategies and directory structure
`/ado-project-onboarding where's the documentation?`	Organized wiki page index with suggested reading

🐙 GitHub Skills — for code on GitHub.com & GitHub Enterprise Cloud

These four skills activate when your code lives on github.com or GitHub Enterprise Cloud (*.ghe.com). They use VS Code's default agent (not the @devops participant) and read your configured GitHub host + default repo automatically, so you never have to specify it.

🔍 GitHub PR Reviewer — `/github-pr-reviewer`

"Review this GitHub PR like a Staff Engineer would."

Try this	What you get
`/github-pr-reviewer review owner/repo#123`	Full review: diffs, risks, security, test coverage, and a verdict
`/github-pr-reviewer what PRs am I waiting on?`	PRs you authored or must review (identity resolved automatically)

Reads CI/Actions check-runs for the head SHA, pulls linked issues for requirements context, and flags failures.

🗂️ GitHub Issue Triage — `/github-issue-triage`

"Turn a noisy backlog into a prioritized triage board."

Try this	What you get
`/github-issue-triage triage issues in owner/repo`	Type, priority, suggested labels and owner per issue
`/github-issue-triage what's assigned to me?`	Issues assigned to you, with duplicate detection and quick wins

🧭 GitHub Repo Onboarding — `/github-repo-onboarding`

"I just cloned this repo — catch me up."

Try this	What you get
`/github-repo-onboarding onboard me to owner/repo`	Structure, build/test setup, branching, CI workflows, where to start
`/github-repo-onboarding who maintains this repo?`	CODEOWNERS, recent contributors, and good first issues

🔧 GitHub Actions Investigator — `/github-actions-investigator`

"Why did my Action fail, and how do I fix it?"

Try this	What you get
`/github-actions-investigator why did my build fail?`	Failing job/step, key error log lines, and a concrete fix
`/github-actions-investigator investigate run <id or url>`	Pass/fail trends, recurring failures, and flaky-test detection

🌐 Azure DevOps + GitHub — One Assistant, Two Worlds

This extension is built around a simple split:

Work items, boards, sprints, pipelines, wikis, test plans → always Azure DevOps.
Code, repositories, pull requests, issues, Actions → Azure DevOps repos or GitHub, your choice.

"Where does your code live?" — the one question you answer once

The first time the extension activates, it asks where your code lives. Pick one:

Choice	What happens
Azure DevOps	GitHub stays disabled. Every code command (`/code`, `/draftpr`, `/createpr`, `/myactivity`) uses ADO.
GitHub.com	Connects to the hosted GitHub MCP server and signs you in. Repo/PR/issue/Actions tools light up.
GitHub Enterprise	Prompts for your Enterprise base URL (e.g. `https://microsoft.ghe.com`), then connects and signs you in.

Re-run anytime with "Git DevOps Assistant: Set up GitHub integration" (Ctrl+Shift+P), or change individual settings under adoProductivity.github.*.

How the assistant knows which host to target

When you run a code command, the assistant determines the effective host by combining your explicit choice above with your workspace's git origin remote:

An explicit mcpServerUrl override wins.
Otherwise, your explicit host choice (GitHub.com / Enterprise / ADO) wins.
The git remote is used as ground truth for the current window.
If GitHub is disabled, all code commands stay on Azure DevOps — even in a GitHub clone.

You never have to tell the assistant "this is a GitHub repo" on every command — it just knows.

What changes per-command once GitHub is enabled

Command	Azure DevOps repo	GitHub / GitHub Enterprise repo
`/createpr`	Creates PR via ADO, links a work item	Creates PR via GitHub MCP — no work item id required
`/draftpr`	Requires a work item id; links work item + diff	No work item id; infers linked issue from branch name (e.g. `fixes #45`)
`/code`	Searches Azure DevOps repos	Searches GitHub via REST — scoped to your repo, correct host & account
`/myactivity`	ADO work items, comments, assignments	Adds a My GitHub Activity section: your open PRs and assigned issues
`/info`	Shows ADO org/project + MCP status	Also shows GitHub host, sign-in, MCP endpoint, and default repo

Set a default repository (recommended)

So the assistant never has to ask "which repo?" (e.g. for "review PR #123"), set:

Setting: adoProductivity.github.defaultRepo = owner/repo
View the current host, sign-in, MCP endpoint and default repo any time with @devops /info.

GitHub Enterprise notes

Enterprise Cloud with data residency (*.ghe.com) — fully supported out of the box; uses a hosted MCP endpoint.
Enterprise Server (self-hosted) — has no remote MCP endpoint. Save your host, then set a custom adoProductivity.github.mcpServerUrl in settings.
When GitHub Enterprise is active, the extension automatically disables VS Code's built-in github.com MCP server so the model never routes operations to the wrong host. It is restored if you switch back or disable GitHub.

🔌 Built-In ADO MCP Server — Zero Setup, Full Power

This extension ships with a pre-configured Azure DevOps MCP Server that connects GitHub Copilot directly to your organization. No API tokens. No server config. It starts when the extension starts.

What that means for you

You can talk to every corner of Azure DevOps in plain English — and the AI figures out which tools to call:

You say	What happens behind the scenes
`@devops show my work items`	`mcp_ado_wit_my_work_items`
`@devops what builds failed today?`	`mcp_ado_pipelines_get_builds`
`@devops list PRs on my branch`	`mcp_ado_repo_list_pull_requests_by_repo_or_project`
`@devops search code for AuthService`	`mcp_ado_search_code`
`@devops find wiki docs about deployment`	`mcp_ado_search_wiki`
`@devops show sprint capacity`	`mcp_ado_work_get_team_capacity`
`@devops create a task under work item 12345`	`mcp_ado_wit_add_child_work_items`

9 Tool Domains — Everything Connected

Domain	What you can do
📝 Work Items	Get, create, update, link, comment — manage your backlog conversationally
🔄 Iterations	Sprint details, team capacity, team settings
🔀 Repositories	PRs, branches, commits, code review threads
⚙️ Pipelines	Builds, pipeline runs, logs, artifacts
🔍 Search	Full-text search across code, wiki, and work items
📖 Wiki	List, read, create, and update wiki pages
🧪 Test Plans	Test plans, suites, cases, and build test results
👥 Core	Projects, teams, and identity lookup
🛡️ Security	Advanced Security alerts for repositories

Follow-ups just work. Ask @devops show failed builds today, then say "Only the ones from the release pipeline" — the server keeps context.

🐙 Built-In GitHub MCP Server — Optional, On When You Need It

When you choose GitHub.com or GitHub Enterprise during setup, the extension registers a second MCP server (Git DevOps Assistant: GitHub MCP Server) that connects GitHub Copilot to your GitHub host.

Authentication: reuses your existing VS Code GitHub sign-in — no PAT, no extra login. OAuth scopes: repo, read:org.
Endpoint routing: github.com → the hosted Copilot MCP endpoint; Enterprise Cloud (*.ghe.com) → your tenant's hosted endpoint; Enterprise Server → your custom mcpServerUrl.
What you can do in plain English:

You say	What happens behind the scenes
`@devops review PR owner/repo#123`	GitHub MCP reads the PR, diffs, and checks
`@devops what issues are assigned to me?`	GitHub REST search scoped to your account
`@devops create a PR for my branch`	GitHub MCP `create_pull_request`
`@devops why did the latest Actions run fail?`	GitHub Actions check-runs + logs

The assistant only loads the GitHub or Azure DevOps tools relevant to your current command, so you stay well under Copilot's per-request tool limit.

🌟 Quick Wins by Role

Developers

Scenario	Command / Skill
Get implementation guidance	`@devops /plan 123456`
Auto-generate PR description	`@devops /draftpr 123456`
Create a PR from current branch	`@devops /createpr`
Prove code meets requirements	`@devops /reqcheck 123456`
Check pipeline / build status	`@devops /build`
Diagnose build failure	`@devops /build 456` or `/ado-release-manager why did build #456 fail?`
Move work item to Active	`@devops /update 123456 state=Active`
Find code across all repos	`@devops /code AuthService`
Get a senior-level PR review	`/ado-pr-reviewer review PR #789`
Check PR test coverage	`/ado-pr-reviewer check test coverage for PR #789`

Scrum Masters & PMs

Scenario	Command / Skill
Sprint dashboard	`@devops /sprint` or `/ado-scrum-master How's our sprint?`
Automated standup prep	`/ado-scrum-master standup summary`
Capacity-aware sprint planning	`/ado-scrum-master plan next sprint`
Data-driven retrospective	`/ado-scrum-master run a retro`
AI-rank the backlog	`@devops /prioritize`
Backlog grooming	`/ado-scrum-master backlog refinement`
Break down a large item	`@devops /decompose 123456 Task`
Quick work item summary	`@devops /summarize 123456`

Testers & QA

Scenario	Command / Skill
Test results from latest build	`@devops /build` or `@devops show test results from latest build`
List test plans	`@devops list all test plans for this sprint`
Find bugs reported today	`@devops what bugs were reported today?`
Check PR test coverage	`/ado-pr-reviewer check test coverage for PR #789`
Search test-related code	`@devops /code TestHelper`

DevOps Engineers

Scenario	Command / Skill
Pipeline dashboard	`@devops /build` or `/ado-release-manager pipeline dashboard`
Build failure root cause	`@devops /build 456` or `/ado-release-manager why did build #456 fail?`
Pre-release checklist	`/ado-release-manager are we ready to release?`
Generate release notes	`/ado-release-manager generate release notes`
Project health score	`/ado-tech-debt-analyzer tech debt report`
Stale PR report	`/ado-tech-debt-analyzer stale PRs`
Security alerts	`/ado-release-manager security check`

New Team Members

Scenario	Command / Skill
Full project walkthrough	`/ado-project-onboarding I'm new here`
Team roster & assignments	`/ado-project-onboarding who's on the team?` or `@devops /sprint`
Find documentation	`/ado-project-onboarding where's the documentation?`
Repository guide	`/ado-project-onboarding what repos do we have?`
Understand current sprint	`@devops /sprint`

GitHub Developers (code on github.com / `*.ghe.com`)

Scenario	Command / Skill
Review a GitHub PR	`/github-pr-reviewer review owner/repo#123`
See PRs I need to review	`/github-pr-reviewer what PRs am I waiting on?`
Triage issues in a repo	`/github-issue-triage triage issues in owner/repo`
Onboard to a new repo	`/github-repo-onboarding onboard me to owner/repo`
Diagnose a failed Actions run	`/github-actions-investigator why did my build fail?`
Draft a PR from current branch	`@devops /draftpr` then `@devops /createpr`
See my GitHub activity	`@devops /myactivity`

📦 Getting Started

Installation

Install the extension
- Open VS Code and press Ctrl+Shift+X (Windows/Linux) or Cmd+Shift+X (Mac)
- Search for "Git DevOps Assistant"
- Click Install
Sign in to Azure DevOps
- After install the extension guides you automatically to Sign In and authenticate
- Complete the authentication flow
Configure your organization and project
- When prompted, enter your Azure DevOps organization URL (e.g., https://dev.azure.com/your-org) or Name (e.g., your-org)
- Enter your project name: Exact project display name or its slug (e.g., MyProject)
- You're all set! 🎉
Choose where your code lives (GitHub setup)
- On first run, the assistant asks "Where does your code live?"
- Pick Azure DevOps (keep everything in ADO), GitHub.com, or GitHub Enterprise
- For GitHub Enterprise, enter your base URL (e.g., https://microsoft.ghe.com)
- Choosing a GitHub option signs you in via your existing VS Code GitHub login and enables repo/PR/issue/Actions tools
- Re-run anytime: Ctrl+Shift+P → "Git DevOps Assistant: Set up GitHub integration"
Open Copilot Chat and go
- Click the chat icon in the Activity Bar or press Ctrl+Shift+I
- Type @devops /help or try any skill from the table above

Pro tip: Run @devops /instruct to auto-generate .github/copilot-instructions.md — this teaches Copilot about your Azure DevOps MCP tools so every future conversation is smarter.

🎮 17 Slash Commands

While natural language and skills handle most scenarios, these slash commands give you quick, focused actions:

Command	What it does	Example
`/help`	List all commands and capabilities	`@devops /help`
`/info`	Show org/project + GitHub host/sign-in status	`@devops /info`
`/instruct`	Generate Copilot instructions for MCP-aware AI	`@devops /instruct`
`/summarize <id>`	Summarize a work item's discussion	`@devops /summarize 123456`
`/decompose <id> <type>`	Break a work item into child items	`@devops /decompose 123456 Task`
`/simplify <id>`	Rewrite as smaller, actionable tasks	`@devops /simplify 123456`
`/plan <id>`	Generate implementation plan mapped to your code	`@devops /plan 123456`
`/prioritize`	AI-rank work items by impact	`@devops /prioritize`
`/myactivity`	Your recent ADO updates + GitHub PRs/issues 🌐	`@devops /myactivity`
`/docs <query>`	Search Azure DevOps wiki	`@devops /docs API guide`
`/code <query>`	Search code on your configured host (ADO/GitHub) 🌐	`@devops /code AuthService`
`/draftpr [id]`	Generate PR description (ADO work item or GitHub) 🌐	`@devops /draftpr 123456`
`/reqcheck <id>`	Verify code meets acceptance criteria	`@devops /reqcheck 123456`
`/build [id]`	View pipeline status, logs, diagnose failures	`@devops /build`
`/update <id> <changes>`	Update work item fields, state, or add comments	`@devops /update 123456 state=Active`
`/sprint [team]`	View sprint status, capacity, and progress	`@devops /sprint`
`/createpr [options]`	Create a PR for the current branch (ADO/GitHub) 🌐	`@devops /createpr`

🌐 = host-aware: automatically targets Azure DevOps or GitHub based on your configured host and the current repo.

Tips

Commands work with follow-up questions: after @devops /myactivity, ask "Show only bugs"
Use /draftpr before creating a PR — never write a PR description by hand again
Use /createpr right after /draftpr — complete the PR workflow without leaving VS Code
Use /reqcheck before closing a work item — prove your code meets every acceptance criterion
Use /plan before starting work — get implementation guidance mapped to your actual codebase
Use /build to check pipeline status — stop switching to the browser for build results
Use /update to change work item state — move items to Active/Resolved without leaving the editor
Use /sprint in standups — get a real-time sprint dashboard instantly

🔧 Configuration & Settings

Check Your Current Configuration

@devops /info

This shows your configured organization and project, with a button to change settings.

Change Organization or Project

Type @devops /info
Click the Change Configuration button in the response
Enter new organization URL and/or project name
Confirm changes

Alternative: Press Ctrl+Shift+P and run "Git DevOps Assistant: Change configuration" from the command palette, but @devops /info + Change Configuration button is the fastest path.

Note: When you change the organization or project, the ADO MCP server automatically reconfigures to point to your new Azure DevOps organization. This ensures all tools and natural language queries work with your updated settings immediately.

Optimize Copilot for Your Azure DevOps Setup

Run @devops /instruct to automatically generate or update .github/copilot-instructions.md with:

Complete list of available Azure DevOps MCP tools
Essential workflows and best practices
Tool call patterns with examples
Your organization and project context

This helps GitHub Copilot provide better suggestions tailored to your Azure DevOps environment. Run it again anytime to refresh with the latest tool information.

Azure DevOps Authentication (Guest / Multi-Tenant)

Most users never need to touch this — the extension signs you in with your default Microsoft account automatically.

If your Azure DevOps organization lives in a different Microsoft Entra tenant than your home/sign-in tenant (a common setup when you're added to another company's ADO as a guest), tokens issued by your home tenant get rejected by Azure DevOps with errors like TF400813: The user is not authorized to access this resource. Point authentication at the right tenant:

Setting	Default	What it does
`adoProductivity.tenantId`	`""`	Microsoft Entra tenant ID (GUID) hosting your ADO org. Empty = your default/home tenant. Set it only for guest/multi-tenant scenarios.

How to find the tenant ID: Azure portal → Microsoft Entra ID → Overview, or your org settings at https://dev.azure.com/{org}/_settings.

After you set or change it, the extension silently re-acquires the token against that tenant and reconfigures the ADO MCP server — no restart needed.

GitHub Settings

All GitHub options live under the adoProductivity.github.* namespace (Ctrl+, → search "Git DevOps Assistant GitHub"):

Setting	Default	What it does
`adoProductivity.github.enabled`	`true`	Master switch for the GitHub MCP server and GitHub commands/skills
`adoProductivity.github.host`	`github.com`	`github.com` or `enterprise`
`adoProductivity.github.enterpriseUri`	`""`	Your GitHub Enterprise base URL (e.g., `https://microsoft.ghe.com`)
`adoProductivity.github.authMode`	`oauth`	`oauth` (recommended) or `token` (inject VS Code session token as bearer header)
`adoProductivity.github.mcpServerUrl`	`""`	Override the MCP endpoint — required for self-hosted GitHub Enterprise Server
`adoProductivity.github.defaultRepo`	`""`	Default `owner/repo` so commands never have to ask which repo

Sign in / switch hosts: Ctrl+Shift+P → "Git DevOps Assistant: Sign in to GitHub" or "Git DevOps Assistant: Set up GitHub integration". Check current status anytime with @devops /info.

The extension adds a Git DevOps Assistant view to your Activity Bar:

Work Items View: Browse and manage work items from your Azure DevOps projects
Work Item Details: View detailed information in a webview
Quick actions: Open in browser, refresh, sort by priority

🗣️ Natural Language Examples

You don't need to memorize commands. Just type @devops and ask in plain English. In Agent Mode, skip the @devops tag entirely — just ask your question and the ADO MCP tools kick in automatically:

Area	Example queries
Work Items	`Show my assigned work items` · `Find high-priority bugs assigned to my team` · `Create a bug titled "Login fails on mobile" assigned to me`
Boards	`What's in the current sprint?` · `Compare completed work items across the last 3 sprints`
Code & Repos	`Find code that implements JWT validation` · `Search all repos for usage of deprecated API`
Pull Requests	`Show my open PRs` · `List PRs waiting for my review` · `PRs targeting main open more than 5 days`
Pipelines	`Show failed builds today` · `Find all builds that failed this week grouped by failure reason`
Tests	`Show test results for the latest build` · `Find flaky tests from the last 2 weeks`
Wiki	`Search wiki for "deployment process"` · `Find wiki articles about security best practices`
Activity	`What did I work on today?` · `Summarize all my activity from the last month`

💡 Pro Tips

Day-to-Day Workflows

When	Do this
Morning standup	`@devops /sprint` or `/ado-scrum-master standup summary`
Before starting work	`@devops /plan 123456`
Pick up a work item	`@devops /update 123456 state=Active`
Before creating a PR	`@devops /draftpr 123456`
Create the PR	`@devops /createpr`
Get a code review	`/ado-pr-reviewer review PR #789`
Before closing a work item	`@devops /reqcheck 123456`
Check build status	`@devops /build` or `/ado-release-manager pipeline dashboard`
Sprint planning	`/ado-scrum-master plan next sprint`
Release day	`/ado-release-manager are we ready to release?`
Onboarding a teammate	`/ado-project-onboarding I'm new to this project`
Tech debt review	`/ado-tech-debt-analyzer tech debt report`

Getting Better Answers

Be specific: "Show failed builds today" beats "Show builds"
Use context: "What PRs are related to work item 123?"
Chain naturally: Ask a question, then refine — "Only show critical", "From last week"

🐛 Troubleshooting

Issue	Solution
Wrong org/project	`@devops /info` → Click Change Configuration
Commands not responding	Make sure Copilot Chat is active and you're using `@devops` prefix
Empty search results	Verify the repo/wiki exists and you have access permissions
Authentication expired	Press `Ctrl+Shift+P` → "Git DevOps Assistant: Refresh Authentication Token"
`TF400813` / "user is not authorized" (guest in another tenant)	Set `adoProductivity.tenantId` to the Entra tenant ID that hosts your ADO org (see Azure DevOps Authentication above)
GitHub commands target the wrong host	`@devops /info` to check the configured host → re-run "Git DevOps Assistant: Set up GitHub integration"
GitHub tools missing / not signed in	`Ctrl+Shift+P` → "Git DevOps Assistant: Sign in to GitHub"; confirm `adoProductivity.github.enabled` is `true`
GitHub Enterprise Server won't connect	GHES has no remote MCP endpoint — set `adoProductivity.github.mcpServerUrl` to your custom server
`Cannot have more than 128 tools per request`	Disable other MCP servers, skills, or agents in the chat tool picker — `@devops` only loads Azure DevOps/GitHub MCP tools, but other host-injected entries still count toward the limit

Still stuck? Try @devops /help → restart VS Code → reinstall the extension.

🔐 Privacy & Security

Authentication: Standard Azure DevOps OAuth flow for ADO; your existing VS Code GitHub sign-in (OAuth scopes repo, read:org) for GitHub — no PATs to manage
Permissions: Only accesses Azure DevOps and GitHub resources you already have rights to
Storage: Configuration stored locally in VS Code settings; tokens managed and refreshed by VS Code's built-in auth providers
Telemetry: Anonymous usage data helps improve the extension

💬 Feedback & Support

Use the VS Code Marketplace Q&A section for questions, bug reports, and feature requests. Your input directly shapes what we build next.

How to Get Help:

Open the Marketplace Page: Search for "Git DevOps Assistant" in VS Code extensions
Navigate to Q&A: Click the "Q&A" tab on the extension's marketplace page
Ask Your Question: Post your issue with relevant details (command run, error message, etc.)
Share Feedback: Let us know what's working well and what could be improved
Report Bugs: Include steps to reproduce and expected vs. actual behavior

Your questions and suggestions help us continuously improve the extension!

Your Azure DevOps workflow just changed forever. Type @devops /help to begin. 🚀

Git DevOps Assistant (MCP Powered)

Microsoft

Git DevOps Assistant (MCP Powered)

ℹ️ Important Notice

🎬 Get Set Up in Under 2 Minutes

🔄 How It Works — End-to-End

First-Run Setup Flow

Where your code lives — ADO vs GitHub vs GitHub Enterprise

🧠 9 AI Skills — Your Team's Superpowers

🏃 Scrum Master — /ado-scrum-master

🔍 PR Reviewer — /ado-pr-reviewer

🚀 Release Manager — /ado-release-manager

🏥 Tech Debt Analyzer — /ado-tech-debt-analyzer

🎯 Project Onboarding — /ado-project-onboarding

🐙 GitHub Skills — for code on GitHub.com & GitHub Enterprise Cloud

🔍 GitHub PR Reviewer — /github-pr-reviewer

🗂️ GitHub Issue Triage — /github-issue-triage

🧭 GitHub Repo Onboarding — /github-repo-onboarding

🔧 GitHub Actions Investigator — /github-actions-investigator

🌐 Azure DevOps + GitHub — One Assistant, Two Worlds

"Where does your code live?" — the one question you answer once

How the assistant knows which host to target

What changes per-command once GitHub is enabled

Set a default repository (recommended)

GitHub Enterprise notes

🔌 Built-In ADO MCP Server — Zero Setup, Full Power

What that means for you

9 Tool Domains — Everything Connected

🐙 Built-In GitHub MCP Server — Optional, On When You Need It

🌟 Quick Wins by Role

Developers

Scrum Masters & PMs

Testers & QA

DevOps Engineers

New Team Members

GitHub Developers (code on github.com / *.ghe.com)

📦 Getting Started

Installation

🎮 17 Slash Commands

Tips

🔧 Configuration & Settings

Check Your Current Configuration

Change Organization or Project

Optimize Copilot for Your Azure DevOps Setup

Azure DevOps Authentication (Guest / Multi-Tenant)

GitHub Settings

🖥️ Sidebar Views

🗣️ Natural Language Examples

💡 Pro Tips

Day-to-Day Workflows

Getting Better Answers

🐛 Troubleshooting

🔐 Privacy & Security

💬 Feedback & Support

How to Get Help:

🏃 Scrum Master — `/ado-scrum-master`

🔍 PR Reviewer — `/ado-pr-reviewer`

🚀 Release Manager — `/ado-release-manager`

🏥 Tech Debt Analyzer — `/ado-tech-debt-analyzer`

🎯 Project Onboarding — `/ado-project-onboarding`

🔍 GitHub PR Reviewer — `/github-pr-reviewer`

🗂️ GitHub Issue Triage — `/github-issue-triage`

🧭 GitHub Repo Onboarding — `/github-repo-onboarding`

🔧 GitHub Actions Investigator — `/github-actions-investigator`

GitHub Developers (code on github.com / `*.ghe.com`)