macios-ci-postmortem

To investigate flaky tests in macOS and iOS CI pipelines, this skill automates post-mortem analysis by collecting recent PR-validation builds and isolating failing tests from the last seven days. It classifies failures and suggests GitHub issue actions to track fixes.

Automating CI postmortems for dotnet/macios builds involves collecting recent PR failures, classifying them as flaky tests or infrastructure issues, and proposing GitHub issue actions like creating, commenting, or reopening tickets to drive remediation across shared regressions.

You can track shared CI regressions across recent pull requests because the skill performs cross-project correlation, grouping failures into shared regression or PR-specific categories to identify systemic build issues and surface root causes.

The macios CI postmortem workflow does suggest GitHub issue actions for infrastructure failures, preparing stakeholder summaries and proposing whether to create, comment on, or reopen issues to drive remediation for build pipelines.

CI failures are classified into flaky tests, infrastructure issues, shared regressions, or PR-specific problems when investigating dotnet/macios build errors, storing the findings in a database to prioritize fixes over the last week.