pipelines-build-summary
List, inspect, and troubleshoot Azure DevOps pipeline builds. Shows recent builds for a pipeline definition, drills into a specific build's status and result, displays logs for failed steps, and lists the changes associated with a build.
- Installs
- 124
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/microsoft/azure-devops-skills --skill pipelines-build-summary- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads pipelines-build-summary automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Pipeline build summary
This skill works in the context of a project. A pipeline definition or build ID is optional and depends on what the user asks.
Project selection
- If the user provides a project name in their request (for example, "for Contoso"), use that project directly and do not call
core_list_projects. - If the user does not provide a project name, first ask the user once to provide the project name.
- If the project name is still not provided after asking once, call
core_list_projectsto return a list of projects the user can choose from.
Pipeline definition selection
- If the user provides a pipeline or definition name, use
pipelines_definitionwith actionlistand anamefilter to find it. - If the user does not specify a pipeline and the request requires one (for example, "show recent builds"), ask the user once for the pipeline name.
- If the pipeline name is still not provided after asking once, call
pipelines_definitionwith actionlistto list available definitions for the user to choose from.
Tools
Use Azure DevOps MCP Server tools for all interactions with Azure DevOps.
core_list_projects: Get a list of projects in the organization.pipelines_definition(action:list): Get a list of build/pipeline definitions for a project.pipelines_build(action:list): Get a list of builds, optionally filtered by definition, branch, or status.pipelines_build(action:get_status): Get the status and result of a specific build by ID.pipelines_build_log(action:list): Get the list of logs for a specific build.pipelines_build_log(action:get_content): Get a specific log by log ID for a build (use to retrieve failed step logs).pipelines_build(action:get_changes): Get the commits/changes associated with a specific build.
Rules
1. List recent builds for a pipeline
- When the user asks to list builds or show recent builds for a pipeline, call
pipelines_buildwith actionlistfiltered by the definition ID. - Optionally filter by
branchName,statusFilter, orresultFilterif the user specifies (for example, "failed builds on main"). - Do not fetch logs or changes unless the user asks.
- Show the results in a table.
- If there are no builds, explicitly state that there are no builds for this pipeline.
Example
- "show recent builds for pipeline 'CI-Main' in project Contoso"
2. Get build status by ID
- When the user asks about a specific build (for example, "build 12345"), call
pipelines_buildwith actionget_statuswith that build ID. - Show the build number, status, result, source branch, start/finish time, requested by, and definition name.
- If the build failed, suggest viewing the logs.
Example
- "what is the status of build 12345 in project Contoso?"
3. View logs for a failed build
- When the user asks to view logs or why a build failed, first call
pipelines_build_logwith actionlistto get the list of all log entries for the build. - Identify failed steps from the log list (look for steps that indicate errors or failures).
- Call
pipelines_build_logwith actionget_contentfor the relevant failed log entries to retrieve the actual log content. - Present the log output in a code block so it is easy to read.
- Do not dump all logs. Focus on the failed steps and the last portion of each relevant log.
Example
- "show me the logs for build 12345 in project Contoso"
- "why did build 12345 fail?"
4. List changes for a build
- When the user asks to see what changed or list commits for a build, call
pipelines_buildwith actionget_changeswith the build ID. - Show the results in a table with commit ID, author, and message.
- If there are no changes, explicitly state that there are no changes associated with this build.
Example
- "what changes were in build 12345?"
- "list commits for build 12345 in project Contoso"
Display results
When displaying build lists, show the following in a table:
- Build ID as a clickable hyperlink in this format:
[{buildId}](https://dev.azure.com/{organization}/{project}/_build/results?buildId={buildId}) - Definition name
- Status (for example: completed, inProgress, cancelling, notStarted)
- Result (for example: succeeded, failed, canceled, partiallySucceeded) — use emoji: ✅ succeeded, ❌ failed, ⚠️ partiallySucceeded, 🚫 canceled
- Source branch
- Start time formatted as
MM/DD/YYYY HH:MM - Requested by (display name only)
When displaying a single build's status, show all the above fields plus:
- Finish time formatted as
MM/DD/YYYY HH:MM - Build number
- Duration (calculated from start and finish time)
When displaying changes, show in a table:
- Commit ID (short hash, first 8 characters)
- Author
- Message (first line only)
- Timestamp
FAQ
What does the pipelines-build-summary skill do?
List, inspect, and troubleshoot Azure DevOps pipeline builds. Shows recent builds for a pipeline definition, drills into a specific build's status and result, displays logs for failed steps, and lists the changes associated with a build.
How do I install pipelines-build-summary?
Run npx skills add https://github.com/microsoft/azure-devops-skills --skill pipelines-build-summary in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/pipelines-build-summary/ (personal) or .claude/skills/pipelines-build-summary/ (project).
Which AI agents can use pipelines-build-summary?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is pipelines-build-summary safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains pipelines-build-summary?
It is published by microsoft in microsoft/azure-devops-skills, and it is an official skill from the maker of the technology it covers. It has 124 recorded installs.
More from microsoft/azure-devops-skills
boards-work-item-summary
microsoft/azure-devops-skills
Open the skill to read its SKILL.md instructions.
boards-my-work
microsoft/azure-devops-skills
Open the skill to read its SKILL.md instructions.
work-iterations
microsoft/azure-devops-skills
List, create, and assign iterations for Azure DevOps projects and teams.
security-alert-review
microsoft/azure-devops-skills
List and review Advanced Security alerts for an Azure DevOps repository. Shows dependency vulnerabilities, secret exposure, and code scanning findings with filtering by severity, state, and alert type.
skill-name
microsoft/azure-devops-skills
Description of what the skill does and when to use it
boards-backlog-summary
microsoft/azure-devops-skills
Get the team's Requirements-level backlog (Product Backlog Items and Bugs) filtered to Active items assigned to the current user. Shows parent/child hierarchy and sorts by priority. Use this skill when the user wants to see their backlog items, sprint assignments, or work they own on a team board.
Popular devops & cloud skills
microsoft-foundry
microsoft/azure-skills
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure
azure-diagnostics
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
azure-prepare
microsoft/azure-skills
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.
azure-ai
microsoft/azure-skills
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
azure-deploy
microsoft/azure-skills
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
azure-validate
microsoft/azure-skills
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.