AGENT SKILL

update-roslyn-version

Update all Roslyn dependency versions in the razor repository. Use this when asked to update, bump, or change the Roslyn version.

License 许可
MIT
最近更新
2026-11-10
Stars
★ 1
Forks
0

01 前言 Front Matter

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.

03 SKILL.md 正文

Update 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).

Steps

  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>.

  2. 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.

  3. Update eng/Version.Details.xml: Replace all Roslyn <Dependency> elements' Version attributes with the new version.

  4. Run restore.cmd (or restore.sh on non-Windows) from the repo root to download the new packages. Wait for it to complete successfully.

  5. 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.

  6. 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.

  7. Verify by running git diff to confirm only the expected version and SHA changes were made in the two files.

Notes

  • Do NOT modify non-Roslyn dependencies (arcade, aspnetcore, runtime).
  • The NuGet cache path may vary by machine. Common locations:
    • Windows: D:\NugetCache or %USERPROFILE%\.nuget\packages
    • macOS/Linux: ~/.nuget/packages
  • If restore fails, the version may not exist on the configured NuGet feeds — verify the version string.

04 同仓库更多 Skills

YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

vercel-sandbox

Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

slack

Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

electron

Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

dogfood

Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

shadcn

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.

★ 1