.NET Remote Testing

Do this now

You were invoked. That is the request. Run the tests.

Your first action is this command — not a question, not a menu, not a summary of what you could do:

dotnet run --file "<skill-root>/scripts/remote-test.cs" -- run --repo-root "<repo-root>"

Run it immediately, then report the result. This holds for a bare /dotnet-remote-testing with no other words, and for "remote test this repo", "run my tests in Docker", or any equivalent. There is nothing to clarify first: the runner resolves the environment, the target, and the configuration by itself, and it is the only thing that decides whether a question is needed.

Forbidden as a first response: listing your capabilities; "here are the typical workflows"; offering list / plan / run as choices; asking which project, environment, .NET version, or filter to use; asking for confirmation. If you are about to write "What would you like me to do?", you have already failed — run the command instead.

You may ask a question in exactly one situation: the command exited 16 (SelectionRequired), which means a genuine choice remains. Then ask one question listing only the candidates it returned, and rerun with -e <name>. Every other exit code is an outcome to report, never a question. The full mapping is in Failure handling.

Resolve the two placeholders exactly once and reuse them verbatim: