mav-bp-cicd-azure

Monitor Azure DevOps pipeline status after pushes until CI passes.

10|2|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/thermiteau/maverick --skill mav-bp-cicd-azure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mav-bp-cicd-azure
Source: https://github.com/thermiteau/maverick/tree/main/skills/mav-bp-cicd-azure
Command: npx skills add https://github.com/thermiteau/maverick --skill mav-bp-cicd-azure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After pushing, monitor Azure DevOps pipelines and do not declare work complete until CI passes. This ensures unverified deployments are not considered done.

Core Features & Use Cases

  • Monitor pipeline status after push to confirm CI passes.
  • Diagnose failures and read logs quickly to identify root causes.
  • Respect pipeline boundaries by ensuring work completion only after successful CI.

Quick Start

After pushing your changes, instruct the agent to check the Azure DevOps pipeline status and wait for CI to pass before marking the task complete.

Frequently Asked Questions about mav-bp-cicd-azure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor Azure DevOps pipelines after a push to ensure CI passes?

To monitor Azure DevOps pipelines after a push, use Azure CLI with the DevOps extension or REST API access via a personal access token. This ensures CI passes before work is declared complete.

What's the best way to diagnose Azure DevOps CI failures from pipeline logs?

Diagnosing Azure DevOps CI failures involves reading pipeline logs to identify root causes after a push. This approach respects pipeline boundaries by ensuring work completion only after successful CI.

Do I need Azure CLI to check Azure DevOps pipeline status?

You do not strictly need Azure CLI to check Azure DevOps pipeline status; you can also use REST API access authenticated with a personal access token to monitor CI gating and pipeline results.

Can I modify Azure DevOps pipeline definitions when monitoring CI status?

You cannot modify Azure DevOps pipeline definitions when monitoring CI status. The process strictly observes pipeline boundaries and tracks results without altering existing pipeline configurations.

When should I use automated CI gating for Azure DevOps pushes?

Automated CI gating for Azure DevOps pushes should be used on projects and branches where CI gating is enforced. It prevents unverified deployments from being considered done by requiring successful pipeline completion.