菜单
Update all Roslyn dependency versions in the razor repository. Use this when asked to update, bump, or change the Roslyn version.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| name | update-roslyn-version |
| description | Update all Roslyn dependency versions in the razor repository. Use this when asked to update, bump, or change the Roslyn version. |
Update all Roslyn dependency versions in the razor repository. The user will provide the new version number (e.g. 5.5.0-2.26118.1).
Identify the current Roslyn version by reading eng/Version.Details.xml — look at the Version attribute on any <Dependency> element with <Uri>https://github.com/dotnet/roslyn</Uri>.
Update eng/Version.Details.props: Replace all Roslyn package version values (in the <!-- dotnet/roslyn dependencies --> section) with the new version. These are the *PackageVersion elements. The old value may be a -dev placeholder or a full version string.
Update eng/Version.Details.xml: Replace all Roslyn <Dependency> elements' Version attributes with the new version.
Run restore.cmd (or restore.sh on non-Windows) from the repo root to download the new packages. Wait for it to complete successfully.
Get the commit hash: After restore, find a .nuspec file for one of the restored Roslyn packages in the NuGet cache (D:\NugetCache on this machine). For example:
D:\NugetCache\microsoft.codeanalysis.common\<NEW_VERSION>\microsoft.codeanalysis.common.nuspec
Parse the <repository commit="..."> element from the nuspec to extract the commit SHA. All Roslyn packages share the same commit.
Update the commit SHA in eng/Version.Details.xml: Replace the old Roslyn <Sha> values with the new commit hash from step 5. Only update Roslyn entries (those with <Uri>https://github.com/dotnet/roslyn</Uri>), not arcade/aspnetcore/runtime entries.
Verify by running git diff to confirm only the expected version and SHA changes were made in the two files.
D:\NugetCache or %USERPROFILE%\.nuget\packages~/.nuget/packagesImport Razor formatting log zips that the user has already downloaded from Azure DevOps feedback tickets or GitHub issues into FormattingLogTest, validate whether the captured problem still reproduces, and if needed drive a minimal repro plus fix workflow.
Run the razor-toolset-ci pipeline to validate the current branch against large third-party repositories (MudBlazor, OrchardCore, ASP.NET Core, etc.). Use when asked to run toolset tests, ecosystem tests, or third-party validation.
Analyze CI build and test status from Azure DevOps and Helix for dotnet repository PRs. Use when checking CI status, investigating failures, determining if a PR is ready to merge, or given URLs containing dev.azure.com or helix.dot.net. Also use when asked "why is CI red", "test failures", "retry CI", "rerun tests", "is CI green", "build failed", "checks failing", or "flaky tests".
Review code changes in dotnet/razor for correctness, performance, and consistency with project conventions. Use when reviewing PRs or code changes.
Analyze VMR codeflow PR status for dotnet repositories. Use when investigating stale codeflow PRs, checking if fixes have flowed through the VMR pipeline, debugging dependency update issues in PRs authored by dotnet-maestro[bot], checking overall flow status for a repo, or diagnosing why backflow PRs are missing or blocked.