macios-ci-postmortem

Classify CI failures from recent dotnet/macios PRs and suggest GitHub issue actions.

2.9k|576|Updated Apr 20, 2016

Search Tags:#ios #macos #infrastructure #postmortem #ci #flaky-tests #github-issues

Ready to run

npx skills add https://github.com/dotnet/macios --skill macios-ci-postmortem

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: macios-ci-postmortem
Source: https://github.com/dotnet/macios/tree/main/.agents/skills/macios-ci-postmortem
Command: npx skills add https://github.com/dotnet/macios --skill macios-ci-postmortem

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates and guides post-mortem analysis of CI failures for dotnet/macios, enabling teams to quickly identify flaky tests, infrastructure issues, and shared regressions across recent PRs.

Core Features & Use Cases

Automated discovery: Collects recent PR-validation builds from AzDO and isolates failing tests and infrastructure errors.
Classification & outcomes: Groups failures into flaky, infrastructure, shared regression, or PR-specific categories, then suggests remediation actions.
Issue management: Proposes GitHub issue actions (create, comment, or reopen) and prepares summaries for stakeholders.
Use Case: Run this when investigating CI postmortems to surface root causes and track fixes over the last week.

Quick Start

Run the weekly postmortem workflow against the macios CI to surface failures and recommended actions.

Frequently Asked Questions about macios-ci-postmortem

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

FAQPage Schema

How do I investigate flaky tests in macOS and iOS CI pipelines?▼

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.

What is the best way to automate CI postmortems for dotnet/macios builds?▼

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.

Can I track shared CI regressions across recent pull requests?▼

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.

Does the macios CI postmortem workflow suggest GitHub issue actions for infrastructure failures?▼

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.

How are CI failures classified when investigating dotnet/macios build errors?▼

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.