Creates or updates Known Build Error issues in dotnet/runtime from CI failures.
npx skills add https://github.com/dotnet/runtime --skill create-kbe
Please help me install this Agent Skill. Skill: create-kbe Source: https://github.com/dotnet/runtime/tree/main/.github/skills/create-kbe Command: npx skills add https://github.com/dotnet/runtime --skill create-kbe
CI failures in dotnet/runtime that are not caused by a PR still block merges and waste triage effort. This Skill turns an actionable CI failure into a properly deduplicated Known Build Error (KBE) issue so Build Analysis can track it instead of rerunning CI.
Known Build Error issue in dotnet/runtime from a concrete CI failure with a stable, actionable signature.Use the create-kbe skill to file a Known Build Error issue for this outer-loop CI failure after checking for duplicates.
High-intent search queries and answers about installing and using this skill.
Invoke this Skill with a concrete CI failure candidate. It follows the shared instructions in .github/workflows/shared/create-kbe.instructions.md to search existing KBEs, build the issue body from the template, and file the issue only when the signature is stable and actionable.
A failure should become a KBE when it is actionable, not caused by the PR, and not already recognized by Build Analysis. If the failure is already known or handled by existing triage, the Skill skips filing to avoid duplicates.
No. If the failure is not caused by the PR, the rule is to file or update a Known Build Error instead of rerunning CI. Reruns are avoided because Build Analysis tracks occurrence data in the issue body.
It searches existing open and recently closed KBEs before filing and enforces one failure shape per KBE outcome. If a matching issue exists, it skips creation rather than commenting, since Build Analysis tracks occurrences in the issue body.
The Skill only emits a KBE when the failure signature is stable and actionable. Ambiguous or unstable failures are deferred for human review, and it depends on the caller workflow having correctly scoped the failure candidate.
CoolCoderSuperAnalyze Azure DevOps and Helix CI failures for dotnet repository PRs.
withzombiesAutomate bug fixing from issue creation through regression testing and closure.
DengNaichenAnalyze Swift test suites for flaky patterns and concurrency issues.
dotnetQuarantine or disable flaky tests in dotnet/aspire using QuarantineTools.