CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

analyze-ci-failures

Analyze CI failures on Azure SDK for .NET pull requests and post a comment with how-to-fix instructions. Use when a PR has failing checks, CI is red, or someone asks for help fixing CI.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

—

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Skill: analyze-ci-failures

Analyze CI failures on an Azure SDK for .NET pull request and post a GitHub comment with actionable fix instructions.

When Invoked

Trigger phrases: "analyze CI failures", "fix CI", "why is CI failing", "help with CI", "analyze PR checks", "CI is red", "failing checks".

Inputs

The user must provide a PR number, PR URL, or pipeline build ID. If not provided, ask the user.

An automatic caller also supplies the immutable PR head SHA, check run ID, and completion timestamp. Analyze that completion only, not a newer run. Check-run events do not expose run_attempt; a changed completion timestamp distinguishes another attempt when the provider reuses its check ID. Follow the caller's safe-output and duplicate-prevention contract instead of posting directly.

Workflow

1. Gather information

  • Fetch PR details, check statuses, changed files, and workflow runs using GitHub MCP tools.
  • When a caller supplies a completion identity, verify the PR is still open, non-draft, and at that head, and that the check still identifies the same completed failure. Stop without commenting if it is superseded. Retrieve errors from that run/attempt only; other current check statuses are context, not evidence for its diagnosis.
  • Extract service directory and package name from changed file paths (sdk/<service>/<package>/).
  • Identify the CI provider from each failed check URL before fetching logs:
    • For an Azure DevOps URL (dev.azure.com), extract the buildId. Use azure-sdk-mcp:azsdk_analyze_pipeline when available.
    • If that tool is unavailable, query the public Azure DevOps timeline API with curl: https://dev.azure.com/<organization>/<project>/_apis/build/builds/<buildId>/timeline?api-version=7.1. Inspect issues on failed task records first. If the issues are insufficient, fetch the failed record's log.url.
    • For a GitHub Actions URL, use github-mcp-server-get_job_logs with return_content: true.
  • Do not use GitHub Actions job-log tools for Azure DevOps checks; their job IDs and run IDs are unrelated.

2. Identify failures

Classify each failure using the CI check mapping and log symptom patterns below. Also inspect the PR's code directly (e.g., read generated files for compile errors, check for missing scaffolding files).

Diagnosis must be based on the failed task's actual error text:

  • Quote the decisive error and name the affected file or project.
  • Do not infer the root cause from the check name, because Build/Pack jobs also run changelog verification, package validation, and ApiCompat.
  • Do not call a failure transient or flaky unless the logs contain infrastructure evidence (for example, an agent disconnect, timeout, service outage, or network failure). A documentation-only last commit does not establish flakiness because packaging validates files such as CHANGELOG.md.
  • If logs cannot be retrieved, state that the root cause is unconfirmed and provide the failed task link. Do not substitute a guessed compilation or ApiCompat diagnosis.

3. Post a comment

Compose a GitHub comment with:

  • Header: ## 🔍 CI Failure Analysis for PR #<number>
  • Summary table: All checks with ✅ ❌ ⏳ status
  • Per-failure sections: Specific to THIS PR — include actual error messages, affected files, and concrete fix commands with <service>/<package> filled in
  • Quick fix command at the end if applicable

Before posting, check existing bot comments for the same PR/head/CI run/completed attempt, not just the ## 🔍 CI Failure Analysis header. An older report must not suppress analysis of a new failure. Preserve the caller's exact completion marker when provided; the standalone workflow adds and verifies its marker deterministically at publication.

CI Check Name → Failure Mapping

These are the Azure DevOps and GitHub checks that run on SDK PRs. The check names are repo-specific and not discoverable from general knowledge.

Check Name PatternWhat It ValidatesKey Script
Build Analyze PRBatchUmbrella: code generation, API export, snippets, spelling, CPM, build + packeng/scripts/CodeChecks.ps1
Verify Generated CodeGenerated code matches what the generator produceseng/scripts/CodeChecks.ps1
Validate CPM ComplianceCentral Package Management policyeng/scripts/Validate-CpmCompliance.ps1
Build / PackCompilation + package validation, including changelog verification and ApiCompatdotnet pack
AnalyzeSamples, READMEs, snippets compileeng/scripts/Build-Snippets.ps1
check-spellingSpell-checking changed filescspell via eng/common/scripts/check-spelling-in-changed-files.ps1
verify-linksMarkdown link validationeng/common/scripts/Verify-Links.ps1
checkenforcerMeta-check: waits for all other checks to pass.github/workflows/event-processor.yml

Log Symptom → Root Cause Mapping

These are exact strings/patterns to search for in CI logs. They are specific to this repo's scripts and not inferrable from general knowledge.

Log symptomRoot causeCategory
Generated code is not up to dateGenerated code out of syncRegenerate code
git diff --exit-code failure in CodeChecksGenerated or API files changed after re-running scriptsRegenerate + export API
error CS####:C# compilation errorBuild failure — inspect the specific error code
Build FAILEDCompilation failureBuild failure
MembersMustExist / TypesMustExistApiCompat breaking change (only surfaces in dotnet pack)API compatibility
changelog entry has the following sections with no contentRelease-dated changelog contains empty template sectionsChangelog validation
ChangeLog verification failed / Verify-ChangeLog.ps1Changelog format or content validation failed; use the preceding error for the exact issueChangelog validation
ManagePackageVersionsCentrally / VersionOverrideCPM policy violationCPM compliance
cspell unknown wordsSpelling error in code or API surfaceSpelling
Spell check failedSpelling error in API surface filesSpelling
README instruction format / NuGet\\Install-PackageREADME uses wrong install format (must use dotnet add package)README validation
verify-links broken URLBroken markdown linksLink verification
Path length exceededFile path > 210 charsFile path issue

New Package Checklist

For PRs that introduce a new SDK package (all files are added, no prior version exists), also check for these commonly missing scaffolding files:

Use this checklist only to explain a CI failure, not as an independent code review or a source of unrelated findings.

  • CHANGELOG.md
  • README.md
  • Directory.Build.props (must import parent props)
  • ci.mgmt.yml (for management-plane) or CI pipeline config
  • api/*.cs (public API surface listings — generated via Export-API.ps1)
  • assets.json (test recording assets)

Without ci.mgmt.yml, the Azure DevOps CI pipeline won't trigger — this is a common reason for checkenforcer staying permanently pending.

Repository

Azure/azure-sdk-for-net

Path

.github/skills/analyze-ci-failures/SKILL.md

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.