aurelienclere-365/ado-cowork-plugin/ado-repositories

ADO Repositories

Browse Azure DevOps Git repositories, explore files and folders, view branch lists, read file contents, inspect commit history, and create branches.

When to use

• User wants to list all repositories in a project
• User wants to navigate the file tree of a repository
• User wants to read the content of a specific file
• User wants to see which branches exist
• User wants to create a new branch (e.g. from main for a feature)
• User wants to see commit history for a branch or file
• User wants to find commits by a specific author or in a date range

MCP tools used

Workflow

Listing repositories

1. Call repo_repository(project) — returns all repos with name, ID, default branch,

size, and last update time.

1. Present the Repository List table.

Browsing files

1. Identify: repository name and optional path.
2. Call repo_file(repo, path, branch) with path = "/" for root listing.
3. For a folder: returns child items (files and subfolders).
4. For a file: returns the raw content.
5. If the content is code, present it in a fenced code block with the correct language tag.

Listing branches

1. Call repo_branch(repo) — returns all branches with name, last commit hash,

last commit date, and author.

1. Present the Branch List table.

Creating a branch

1. Identify: repo, new branch name, and source branch (default: main).
2. Confirm with the user before proceeding (branch creation is a write operation).
3. Call repo_create_branch(repo, newBranchName, sourceBranch).
4. Confirm with the new branch name and its source commit.

Commit history

1. Identify: repo, branch (optional), author filter (optional), date range (optional).
2. Call repo_search_commits(repo, branch, author, fromDate, toDate, top).
3. Present the Commit History table.

Output Format

Repository List

Branch List

Commit History

Notes

• File content returned by repo_file is base64-encoded for binary files. For text files,

decode and present as a code block.

• Branch names may contain slashes (e.g. feature/my-feature). Pass them URL-encoded if

the MCP tool requires it.

• Confirm branch creation before calling repo_create_branch — this is a write operation

that cannot be easily undone without repo admin access.

• To read a pipeline YAML file, use repo_file(repo, 'azure-pipelines.yml', branch).

Active context

This skill respects the session context set by the ado-context skill.

• If activeProject is set, use it automatically as the project parameter — do not

ask the user to re-specify it.

• If no context is set and a project is required, invoke Workflow E of ado-context

to resolve it (list projects, ask user to pick, then proceed).