vcpkg CI Failures Analyzer
Overview
Consumes already-collected CI evidence, cross-references it with baselines, and produces a regression
report. If evidence has not yet been collected, invoke fetch-vcpkg-ci-logs first, then return to this
workflow. Do not duplicate its acquisition steps here.
MCP Tools
| Tool |
Purpose |
github-mcp-server-get_file_contents |
Read baseline files |
Prerequisites
- Local failed step logs and relevant extracted failure-log artifacts.
- Build metadata and full Azure build URL.
- For PR builds, PR metadata and full PR URL.
Evidence Acquisition
When the required evidence is not already local, delegate acquisition to a subagent using
fetch-vcpkg-ci-logs. Prefer a fast, low-cost model for this mechanical work. Ask
the subagent to return only the evidence inventory and local paths; keep regression analysis and report
generation in the main agent.
When the evidence is already available locally, proceed directly to analysis.
Workflow
OUTPUT RULE: This skill applies only when the user asked for triage or report output, so a report.md
is always required once it is selected. Write it as soon as step-log analysis completes, then enhance it
from artifacts. Your response MUST also contain the complete report content — not a summary.
URL RULE: Your response text (not just the report file) MUST include:
- For scheduled/manual builds: the full Azure DevOps URL
https://dev.azure.com/vcpkg/public/_build/results?buildId={buildId}
- For PR builds: both the full PR URL
https://github.com/microsoft/vcpkg/pull/{prNumber} AND the Azure DevOps build URL
Before analysis, read .\.github\skills\shared\azure-vcpkg-ci-notes.md.
Phase 1: Analyze failed step logs
Inventory evidence — Confirm the build metadata, failed step-log paths, artifact paths, and triplets
available from the acquisition step.
Scan step logs — Extract every REGRESSION: line and retain exact failure type keywords:
BUILD_FAILED, FILE_CONFLICTS, POST_BUILD_CHECKS_FAILED, and
CASCADED_DUE_TO_MISSING_DEPENDENCIES. Capture 2-3 surrounding lines for context.
PR feature-test logs — PR builds may not have REGRESSION: lines. Instead scan for FAIL:,
failed with, and feature-test error: lines. Capture verbatim:
- Compiler errors (missing headers, undefined symbols)
- Post-build check failures (file path issues, misplaced files)
- Version validation errors
- Platform-specific feature guard messages
Report each feature failure individually. Dependency ports that fail get their own entry.
Version validation — Inspect the "Validate version files" evidence for version database errors.
Write report immediately — Generate and save report.md using the step-log evidence.
Phase 2: Analyze artifacts and enhance
- Analyze artifacts — Read relevant
stdout-{triplet}.log tails and supporting logs. Classify per
references/vcpkg-failure-patterns.md.
- Baselines — Check both
ci.baseline.txt and ci.feature.baseline.txt.
- Enhance report — Add root causes, downstream impact, and actionable recommendations supported by
the evidence.
Report Requirements
Format per references/report-template.md:
- Full build URL:
[{buildNumber}](https://dev.azure.com/vcpkg/public/_build/results?buildId={buildId})
- For PRs:
[#{prNumber}](https://github.com/microsoft/vcpkg/pull/{prNumber})
- List every triplet by full name (e.g.,
x64-windows, arm64-linux) — never "N triplets". Only include triplets that actually had failures for this specific build.
- Use exact failure type keywords from logs:
BUILD_FAILED, POST_BUILD_CHECKS_FAILED, FILE_CONFLICTS, CASCADED_DUE_TO_MISSING_DEPENDENCIES — never paraphrase
- Include error messages verbatim — quote the exact text from logs for compiler errors, path issues, and validation failures
- Dependency ports' failures as separate entries
- Include baseline/known failures — report them with their failure types, but classify them separately from new regressions
Output Structure
Write reports under the session folder from the environment context, alongside the raw evidence, never
into the repository working tree:
{session-folder}/files/ci-failure-analysis/
├── ci-129315/ ← scheduled build
│ └── report.md
└── pr-51202/ ← PR build
└── report.md
Raw evidence stays where fetch-vcpkg-ci-logs placed it, in
{session-folder}/files/ci-failure-logs/; reference those paths from the report instead of copying them.
Critical Rules
- Do not fetch or download logs as part of this skill; use the acquisition skill first.
- Scan step logs first because
FILE_CONFLICTS may appear only there.
- Check both baseline files
- Never suggest
<= version constraints or VCPKG_BUILD_TYPE release
- Clearly distinguish proven root causes from hypotheses and requests for additional diagnostics.
1---2name: analyze-ci-failures3metadata:4 source: https://skillmd.com/skills/microsoft/analyze-ci-failures5 version: 2026-08-146description: >7 Analyze collected vcpkg CI failure evidence, classify regressions and known failures, identify root8 causes, recommend actions, and generate a report by package and triplet.910 USE FOR: explicit requests for CI regression triage, a failure inventory, baseline classification,11 action recommendations, or a formal CI failure report.1213 DO NOT USE FOR: fetching logs as the final output, targeted debugging of one failure, answering a one-off14 question about logs the user pasted or pointed at, general coding, creating ports, or modifying portfiles.15 When requested analysis lacks local evidence, run fetch-vcpkg-ci-logs as the acquisition stage first.1617 **ANALYSIS SKILL** USES: locally collected CI logs, vcpkg baselines, Azure DevOps metadata.18---1920# vcpkg CI Failures Analyzer2122## Overview2324Consumes already-collected CI evidence, cross-references it with baselines, and produces a regression25report. If evidence has not yet been collected, invoke `fetch-vcpkg-ci-logs` first, then return to this26workflow. Do not duplicate its acquisition steps here.2728## MCP Tools2930| Tool | Purpose |31|------|---------|32| `github-mcp-server-get_file_contents` | Read baseline files |3334## Prerequisites3536- Local failed step logs and relevant extracted failure-log artifacts.37- Build metadata and full Azure build URL.38- For PR builds, PR metadata and full PR URL.3940## Evidence Acquisition4142When the required evidence is not already local, delegate acquisition to a subagent using43`fetch-vcpkg-ci-logs`. Prefer a fast, low-cost model for this mechanical work. Ask44the subagent to return only the evidence inventory and local paths; keep regression analysis and report45generation in the main agent.4647When the evidence is already available locally, proceed directly to analysis.4849## Workflow5051> **OUTPUT RULE**: This skill applies only when the user asked for triage or report output, so a `report.md`52> is always required once it is selected. Write it as soon as step-log analysis completes, then enhance it53> from artifacts. Your response MUST also contain the complete report content — not a summary.5455> **URL RULE**: Your response text (not just the report file) MUST include:56> - For scheduled/manual builds: the full Azure DevOps URL `https://dev.azure.com/vcpkg/public/_build/results?buildId={buildId}`57> - For PR builds: both the full PR URL `https://github.com/microsoft/vcpkg/pull/{prNumber}` AND the Azure DevOps build URL5859Before analysis, read `.\.github\skills\shared\azure-vcpkg-ci-notes.md`.6061### Phase 1: Analyze failed step logs62631. **Inventory evidence** — Confirm the build metadata, failed step-log paths, artifact paths, and triplets64 available from the acquisition step.652. **Scan step logs** — Extract every `REGRESSION:` line and retain exact failure type keywords:66 `BUILD_FAILED`, `FILE_CONFLICTS`, `POST_BUILD_CHECKS_FAILED`, and67 `CASCADED_DUE_TO_MISSING_DEPENDENCIES`. Capture 2-3 surrounding lines for context.683. **PR feature-test logs** — PR builds may not have `REGRESSION:` lines. Instead scan for `FAIL:`,69 `failed with`, and feature-test `error:` lines. Capture verbatim:70 - Compiler errors (missing headers, undefined symbols)71 - Post-build check failures (file path issues, misplaced files)72 - Version validation errors73 - Platform-specific feature guard messages74 75 Report each feature failure individually. Dependency ports that fail get their own entry.764. **Version validation** — Inspect the `"Validate version files"` evidence for version database errors.775. **Write report immediately** — Generate and save `report.md` using the step-log evidence.7879### Phase 2: Analyze artifacts and enhance80816. **Analyze artifacts** — Read relevant `stdout-{triplet}.log` tails and supporting logs. Classify per82 [references/vcpkg-failure-patterns.md](references/vcpkg-failure-patterns.md).837. **Baselines** — Check both `ci.baseline.txt` and `ci.feature.baseline.txt`.848. **Enhance report** — Add root causes, downstream impact, and actionable recommendations supported by85 the evidence.8687### Report Requirements8889Format per [references/report-template.md](references/report-template.md):90- Full build URL: `[{buildNumber}](https://dev.azure.com/vcpkg/public/_build/results?buildId={buildId})`91- For PRs: `[#{prNumber}](https://github.com/microsoft/vcpkg/pull/{prNumber})`92- List **every** triplet by full name (e.g., `x64-windows`, `arm64-linux`) — never "N triplets". Only include triplets that actually had failures for this specific build.93- Use **exact** failure type keywords from logs: `BUILD_FAILED`, `POST_BUILD_CHECKS_FAILED`, `FILE_CONFLICTS`, `CASCADED_DUE_TO_MISSING_DEPENDENCIES` — never paraphrase94- Include error messages verbatim — quote the exact text from logs for compiler errors, path issues, and validation failures95- Dependency ports' failures as separate entries96- **Include baseline/known failures** — report them with their failure types, but classify them separately from new regressions9798## Output Structure99100Write reports under the session folder from the environment context, alongside the raw evidence, never101into the repository working tree:102103```text104{session-folder}/files/ci-failure-analysis/105├── ci-129315/ ← scheduled build106│ └── report.md107└── pr-51202/ ← PR build108 └── report.md109```110111Raw evidence stays where `fetch-vcpkg-ci-logs` placed it, in112`{session-folder}/files/ci-failure-logs/`; reference those paths from the report instead of copying them.113114## Critical Rules115116- Do not fetch or download logs as part of this skill; use the acquisition skill first.117- Scan step logs first because `FILE_CONFLICTS` may appear only there.118- Check **both** baseline files119- Never suggest `<=` version constraints or `VCPKG_BUILD_TYPE release`120- Clearly distinguish proven root causes from hypotheses and requests for additional diagnostics.