What problem does it solve?
Reviewing failing CI checks on a .NET MAUI pull request is slow and error-prone: failures may be flaky tests, infrastructure issues, pre-existing base-branch failures, or genuine regressions introduced by the PR. This Skill automates that triage by gathering GitHub, Azure DevOps, and Helix evidence and producing a single merge-readiness verdict.
Core Features & Use Cases
- Deterministic failure attribution: Compares each distinct failure against recent base-branch builds, known-issue registries, and ci-scan history to classify it as Likely PR-caused, Likely unrelated, Needs human investigation, or Insufficient data.
- Hard verdict ceiling: A computed gate caps the overall verdict so a green result is impossible while checks are pending, builds are canceled, device tests are unverified, or legs regressed versus base.
- Structured PR comment output: Posts a compact Tests Failure Analysis comment with badges, a per-failure evidence table, coverage counts, and a recommended action.
- Use Case: A maintainer comments
/review tests on a MAUI pull request with red CI; the Skill gathers context via its PowerShell script, classifies each failure against the base branch, and reports whether the PR's CI is ready to merge.
Quick Start
Ask the agent to review the test failures on a specific dotnet/maui pull request number and report whether its CI is ready to merge.