run-toolset-tests
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.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- run-toolset-tests
- description
- 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.
03 SKILL.md 正文
Run Razor Toolset Tests
Pushes the current branch to dotnet/razor on GitHub and triggers the
razor-toolset-ci
Azure DevOps pipeline (definition 1270, project internal) to build the Razor
compiler toolset and validate it against large third-party projects.
Background
The pipeline lives in the razor-toolset-tests
repo in dnceng/internal. It:
- Builds
Microsoft.Net.Compilers.Razor.Toolsetfrom the Razor repo - Injects it (plus the matching Roslyn toolset) into 11 third-party projects
- Builds each project to verify compatibility
Projects tested: MudBlazor, Havit.Blazor, Telerik Blazor UI, OrchardCore, GrandNode2, Damselfly, Hawaso, dotnet-podcasts, and ASP.NET Core (MVC, Razor Pages, Blazor components).
Important: When manually triggered, the pipeline checks out from the
RazorGitHubRepo resource (github.com/dotnet/razor). The commit must be
pushed to dotnet/razor — commits on forks or the internal ADO mirror are
not accessible for manual runs.
Steps
1. Verify prerequisites
- Confirm we're in the razor repository (look for
src/Compileror check git remotes). - Get the current commit SHA:
git rev-parse HEAD - Get the current branch name:
git branch --show-current(if HEAD is detached, usegit rev-parse --short HEADas the name)
2. Find or configure a remote for dotnet/razor
- Run
git remote -vand look for a remote whose URL containsdotnet/razor. - Common remote names:
upstream,dotnet. - If no such remote exists, add one:
git remote add dotnet https://github.com/dotnet/razor.git - Store the remote name for subsequent steps.
3. Push to GitHub
Push current HEAD to a test branch on dotnet/razor:
git push <remote> HEAD:refs/heads/toolset-test/<branch-name> --force
If the branch name is empty (detached HEAD), use the short SHA instead.
If the push fails with a permission error, inform the user they need push access
to dotnet/razor.
4. Trigger the pipeline
Use the ado-pipelines_run_pipeline MCP tool:
project:"internal"pipelineId:1270resources:{ "pipelines": {}, "repositories": { "RazorGitHubRepo": { "refName": "refs/heads/toolset-test/<branch-name>", "version": "<commit-sha>" } } }
If the MCP tool fails, fall back to the REST API via PowerShell:
$body = @{
resources = @{
repositories = @{
RazorGitHubRepo = @{
refName = "refs/heads/toolset-test/<branch-name>"
version = "<commit-sha>"
}
}
}
} | ConvertTo-Json -Depth 5
az devops configure --defaults organization=https://dev.azure.com/dnceng project=internal
$result = az rest --method post `
--uri "https://dev.azure.com/dnceng/internal/_apis/pipelines/1270/runs?api-version=7.1" `
--body "$body" `
--resource "499b84ac-1321-427f-aa17-267ca6975798" | ConvertFrom-Json
Write-Output "Run URL: https://dev.azure.com/dnceng/internal/_build/results?buildId=$($result.id)"
5. Report results
Show the user:
- The pipeline run URL (from the response, or construct from the build ID)
- The commit SHA and branch that was pushed
- A reminder to clean up the remote branch when done:
git push <remote> --delete toolset-test/<branch-name>
Notes
- All 11 projects run as parallel jobs — individual jobs can fail independently.
- The pipeline uses the
windows.vs2026.amd64agent image. - Pipeline definition: https://dev.azure.com/dnceng/internal/_build?definitionId=1270
- Pipeline source repo: https://dev.azure.com/dnceng/internal/_git/razor-toolset-tests
04 同仓库更多 Skills
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.
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.
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.
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.
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.
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.