Dotnet Buildtools Prereqs Docker Analyze Official Build
dotnet/dotnet-buildtools-prereqs-docker/.github/skills/dotnet-buildtools-prereqs-docker-analyze-official-build
codingOfficial
Official Provider SkillView repo
Analyze supplied evidence for a dotnet-buildtools-prereqs-docker official image build failure, or inspect repository-only context, and return read-only findings and proposed next steps. Use for diagnosis or investigation without live queries, credentials, code execution, edits, builds, pipeline operations, or publication. Not the end-to-end repair workflow.
Files2 files
SKILL.md128 lines
Loading editor…
Install
RecommendedOne command — your agent picks it up automatically.
Select an AI agent above to see the install command.
or
Manual Install
More stepsDownload the archive and add the files to your project manually.
Skill details
Versionv1.0.0
Author.NET
Categorycoding
Skill IDdotnet/dotnet-buildtools-prereqs-docker/.github/skills/dotnet-buildtools-prereqs-docker-analyze-official-build
Files2 files
Related skills
Dotnet Buildtools Prereqs Docker Fix Official BuildRepair failures in the dotnet-buildtools-prereqs-docker Azure DevOps image build, validate with the unofficial test pipeline, and open the appropriate GitHub pull request after the Build stage succeeds. Use only for an explicit request for this end-to-end repair workflow, not read-only investigation or supplied-evidence analysis; those use dotnet-buildtools-prereqs-docker-analyze-official-build.Api ReviewAuthor and file a separate ASP.NET Core API review issue from an originating issue and an implementation pull request or commits. USE FOR writing API review issues, preparing api-ready-for-review proposals, filling API proposal templates, creating API review descriptions from issues and code changes, "fill out the API review", "prepare API review", or opening a pull request that changes public API. DO NOT USE FOR reviewing API design decisions, approving APIs, implementing APIs, or general code Review Public ApiReview a proposed public API for the dotnet/aspnetcore repo the way the @dotnet/aspnet-api-review team would, and recommend concrete changes to the API shape. USE FOR reviewing an API proposal or api-ready-for-review issue, critiquing a ref-assembly diff, deciding whether a new or changed type/method/overload/property should be added at all, evaluating whether an API change or addition is a good idea, changing/extending an existing API or a shipped default/convention, or checking naming/namespacReview Pull RequestCoordinate an identified dotnet/aspnetcore pull request review with independent, source-only topic reviewers without publishing or executing PR code. Use only for top-level orchestration, not delegated topic passes, implementation, CI investigation, or local-diff review.Validate Blazor FeatureValidate a Blazor feature or regression in a real browser using canonical Components samples before selecting permanent coverage. USE FOR exercising src/Components changes with Playwright; choosing the sample or render mode; proving interactivity; checking browser errors; turning a failure into a temporary JavaScript diagnostic assertion; assessing determinism; investigating producer or timing behavior; replacing arbitrary Selenium sleeps with observable waits or gates; choosing a faithful unit-Agentic LabelerLabels issues and pull requests in the dotnet/maui repository with `area-*` and `platform/*` labels ONLY, based on technical content and platform-file conventions. Used by the gh-aw agentic-labeler workflow and available for batch evaluation and interactive Copilot CLI usage.