create-kbe

Creates or updates Known Build Error issues in dotnet/runtime from CI failures.

18.2k|5.6k|Updated Sep 24, 2019

Search Tags:#duplicate detection #triage #build analysis #CI failure #gitHub issues #dotnet runtime #known build error

Ready to run

npx skills add https://github.com/dotnet/runtime --skill create-kbe

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

KBE issue creation: Files a Known Build Error issue in dotnet/runtime from a concrete CI failure with a stable, actionable signature.
Duplicate detection: Searches existing open and recently closed KBEs before filing, enforcing one failure shape per KBE outcome.
Triage decision support: Helps decide whether a candidate failure should become a KBE, be skipped, or be deferred for human review.
Use Case: A scheduled outer-loop CI scanner finds a failing test unrelated to any PR. The Skill checks for existing KBEs, then files a new issue with the failure signature so Build Analysis tracks occurrences in the issue body.

Quick Start

Use the create-kbe skill to file a Known Build Error issue for this outer-loop CI failure after checking for duplicates.

Frequently Asked Questions about create-kbe

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

FAQPage Schema

How do I create a Known Build Error issue in dotnet/runtime?▼

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.

When should a CI failure become a Known Build Error?▼

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.

Does this Skill rerun CI for flaky failures?▼

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.

How does the Skill avoid duplicate Known Build Error issues?▼

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.

What are the limitations of automated KBE creation?▼

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.