Analyzes dotnet/runtime PR CI failures and drafts Known Build Error issues.
npx skills add https://github.com/dotnet/runtime --skill pr-failure-scan
Please help me install this Agent Skill. Skill: pr-failure-scan Source: https://github.com/dotnet/runtime/tree/main/.github/skills/pr-failure-scan Command: npx skills add https://github.com/dotnet/runtime --skill pr-failure-scan
Triaging CI failures on dotnet/runtime pull requests is tedious: you must read Build Analysis output, check AzDO logs, search for existing Known Build Errors (KBEs), and file new issues. This Skill automates that triage loop for a single PR, skipping failures Build Analysis already knows and drafting or filing KBEs only for genuinely new failures.
/pr-failure-scan <PR URL> dryrun to get draft KBE markdown files for each new failure without creating any GitHub issues.Ask the assistant to run /pr-failure-scan on your dotnet/runtime pull request URL, optionally adding dryrun to only produce local draft files.
High-intent search queries and answers about installing and using this skill.
Run /pr-failure-scan with the PR number or URL. The skill reads the Build Analysis check run and failed CI checks for the PR head SHA, skips failures Build Analysis already knows, and drafts or files Known Build Error issues for the rest.
Append the dryrun token to the command, for example /pr-failure-scan <PR URL> dryrun. The skill writes one markdown draft file per new KBE to a session artifact or temporary directory and never creates GitHub issues.
Yes, but the skill compares the PR author with the authenticated GitHub user and requires explicit confirmation first. It warns that any created issues are filed under your account and their content is attributed to you.
Yes. It parses the Build Analysis warning section listing excluded pipelines, inspects the AzDO build, timeline, and logs for those that failed on the PR, and derives failure candidates itself, including draft-only KBEs when evidence is incomplete.
The skill runs the shared KBE lookup flow and, if a match exists that Build Analysis likely missed, reports the matched KBE number and URL with an explanation instead of filing a duplicate issue.
Live mode requires per-issue confirmation because issues are created under the authenticated developer's account. Each prompt shows the proposed title, covered failures, draft file path, and an AI disclosure note is added to the issue body.
heyu-aiVerify CI status, pull request checks, Spectra Amplifier, and worktree safety before merging.
EotelAutomate incremental fixes for TypeScript compilation and build errors.
drunkcodingBisect SGLang CI failures to identify regression-causing PRs or environment changes.
dotnetDiagnose Helix test failures by collecting AzDO timelines, job data, and console logs.