reactor-build-and-check

Diagnose dotnet Reactor builds with structured diagnostics and did-you-mean suggestions.

609|44|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/microsoft/microsoft-ui-reactor --skill reactor-build-and-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reactor-build-and-check
Source: https://github.com/microsoft/microsoft-ui-reactor/tree/main/plugins/reactor/skills/reactor-build-and-check
Command: npx skills add https://github.com/microsoft/microsoft-ui-reactor --skill reactor-build-and-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides guided Reactor build diagnostics by emitting a structured diagnostic stream, skill pointers, and intelligent suggestions to shorten debugging cycles.

Core Features & Use Cases

  • Structured build feedback via mur check with per-line diagnostics and references to known REACTOR_* IDs.
  • Did-you-mean suggestions to correct unknown identifiers and reduce debugging time.
  • Iteration-mode noise suppression to keep focus on blockers; optional final checks for CI readiness.

Quick Start

Run mur check MyApp.csproj to start a guided, iteration-friendly build with structured diagnostics and skill pointers.

Frequently Asked Questions about reactor-build-and-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get structured build diagnostics for dotnet Reactor projects?

Run mur check on your Reactor project to produce a structured diagnostic stream with per-line build feedback, skill pointers, and references to known REACTOR_* identifiers.

Why am I getting unknown identifier errors in my Reactor build and how can I fix them?

Unknown Reactor build identifiers trigger did-you-mean suggestions in the diagnostic stream, helping you correct typos and resolve references to known REACTOR_* IDs quickly.

Can I suppress noise during iterative Reactor development and still run final CI checks?

Iteration-mode noise suppression keeps focus on blockers during active Reactor development, while optional final checks validate CI readiness before merging.

Does this Reactor build diagnostic tool work with both single-file and multi-file workflows?

The diagnostic stream applies to dotnet-based Reactor projects across both single-file and multi-file workflows, supporting iterative debugging and pre-merge checks.

What is the best way to debug analyzer warnings in a Reactor application?

Use mur check to emit a guided diagnostic stream with skill pointers and intelligent suggestions, shortening debugging cycles for analyzer warnings in Reactor builds.