hjemmesidekongen/ai/azure-devops-pipeline

azure-devops-pipeline

Query pipeline status, trigger runs, and parse test results for the active branch via the Azure DevOps MCP server.

MCP requirement

Requires MCP server azure-devops. If not configured:

"MCP server 'azure-devops' not configured — this skill requires it. Add it to your

MCP server list and restart Claude Code."

Stop immediately. Do not simulate or guess pipeline state.

Steps

1. Check MCP — call list-pipelines to verify the server is reachable
2. Get branch — read current branch from git branch --show-current; cross-reference .ai/tasks/active.yml if present
3. Query runs — fetch recent runs for the branch (last 5). Write result to .ai/tasks/<KEY>-pipeline-status.yml
4. Parse test results — if the latest run has a test attachment, extract pass/fail/skipped counts
5. Trigger (if requested) — call trigger-pipeline with branch and any supplied parameters
6. Report — pipeline name, run ID, status (succeeded/failed/running), test counts, artifact links

Trigger mode

Activated when the user says "run pipeline", "trigger build", or similar. Confirm branch and pipeline name before triggering. Report run ID immediately after dispatch.

Output format

Never

• Never guess or infer pipeline status — if MCP is down, stop and say so
• Never trigger a pipeline run without confirming branch and pipeline name first

See references/process.md for output schema, trigger parameters, and anti-patterns.