skills.rest
microsoft
microsoftOFFICIAL
Explore all skills by this author →
Website𝕏@OpenAtMicrosoftGitHub

reactor-devtools

Inspect and drive a running Reactor app via the mur devtools CLI.

609|44|Updated Apr 16, 2026
Search Tags:#automation#debugging#cli#devtools#ui-testing#reactor#winui
One-click install
npx skills add https://github.com/microsoft/microsoft-ui-reactor --skill reactor-devtools
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reactor-devtools
Source: https://github.com/microsoft/microsoft-ui-reactor/tree/main/plugins/reactor/skills/reactor-devtools
Command: npx skills add https://github.com/microsoft/microsoft-ui-reactor --skill reactor-devtools

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reactor developers need a fast, CLI-based way to observe and interact with a running Reactor app to diagnose layout, accessibility, and state-related issues without attaching debuggers or heavy IDE tooling.

Core Features & Use Cases

  • Inspect the live visual tree and render output, including layout bounds, text, and component hierarchy.
  • Drive the app by simulating user actions (click, type, scroll) and read live hook state for UseState/UseEffect-style patterns.
  • Attach to a running app, launch a debug-build, and drive automation via the mur devtools CLI with a rich set of verbs for inspection, switching components, reloading, and logs.

Quick Start

Launch your Reactor app in a devtools-enabled Debug build, then run mur devtools to begin debugging.

Frequently Asked Questions about reactor-devtools

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

FAQPage Schema
How do I debug a Reactor app's visual layout from the command line?▼

Debug a Reactor app's visual layout from the CLI by launching a Debug build and running the mur devtools CLI to inspect bounds, capture screenshots, and read the component hierarchy.

Can I simulate user interactions like clicks and text input via CLI for Reactor apps?▼

Yes, you can simulate user interactions via CLI by using the mur devtools verbs to drive a running Reactor app, simulating clicks, text input, and scroll actions to test interactions.

What is the best way to read live hook state in a running Reactor app without an IDE?▼

The best way to read live hook state without an IDE is using the mur devtools CLI, which attaches to a running Debug build to read useState and useEffect patterns across mounted components.

Does Reactor devtools require a specific build configuration to inspect the visual tree?▼

Yes, Reactor devtools requires a devtools-enabled Debug build to attach to the running app and inspect the visual tree, render output, and layout bounds.

How do I switch components or reload a Reactor app during a debugging session?▼

Switch components or reload a Reactor app during a debugging session by executing the specific inspection and reloading verbs provided by the mur devtools CLI.

Why does my Reactor app need a Debug build for CLI-driven UI testing?▼

Your Reactor app needs a Debug build for CLI-driven UI testing because the devtools integration exposes hook state and visual tree inspection endpoints only in debug-enabled configurations.

Related Skills

Explore More Software Engineering Skills→
kusutorikusutori

reactor-devtools

Automate UI interactions and inspect visual trees in Reactor apps via Mur Devtools.

Community
Advanced
JubaKitiashviliJubaKitiashvili
41

debug-visual

Capture and analyze app screenshots to identify visual issues in React Native/Expo apps.

Community
Advanced
tranceetrancee

asserting-bounds-and-dimensions

Verify Jetpack Compose layout measurements and positioning with dp-typed assertions.

Community
Intermediate
jleechanorgjleechanorg

node-inspect-debugger

Drive Node.js debugging sessions using the V8 inspector and Chrome DevTools Protocol.

Official
Intermediate