dotnet/skills PR #866 — Process API skill for .NET 11 — PR #866
dotnet/skills · pull request #866 ·
Transcript
PlainEnglish
We're looking at pull request eight sixty-six, which brings a new skill guide for the .NET 11 Process API. This is a documentation-focused change with two hundred twenty-nine additions across three files.
PlainEnglish
The pull request pursues three main goals. First, we're documenting new Process APIs that shipped with .NET 11. Second, we're providing practical examples so developers can actually use these APIs in real-world scenarios. And third, we're adding test scenarios that validate the skill activates correctly. Throughout all of this, the skill needs to be registered in the plugin directory so it's discoverable.
PlainEnglish
The .NET 11 runtime introduced significant improvements to the Process API. Before, developers had to manually redirect streams, which was error-prone and could deadlock. Child processes would persist even after the parent exited, leading to resource leaks. With .NET 11, we get convenience methods like RunAndCaptureTextAsync that handle the complexity safely, plus lifecycle properties like KillOnParentExit that tie child process cleanup to the parent. This skill documents those modern APIs so developers can move away from the legacy patterns.
Architecture
Let's see where these changes live. The new skill is created under the dotnet eleven plugin directory, matching the structure of existing skills. We have the main skill documentation in SKILL dot MD, the plugin registration update in the dotnet eleven README, and a new test directory with evaluation scenarios in eval dot yaml. Three files total, all net-new additions.
Architecture
Here's the heart of the new skill documentation. It introduces seven new APIs that shipped with .NET 11. Two of the most impactful are RunAndCaptureTextAsync, which captures process output without deadlock risk, and the KillOnParentExit property, which ties child process lifetime to the parent. Each API gets a signature, a description, and guidance on when to use it.
Architecture
The skill includes four working code examples that cover the most common process orchestration scenarios. Example one demonstrates deadlock-free output capture using RunAndCaptureTextAsync. Example two shows how KillOnParentExit ensures child processes are cleaned up automatically. Example three walks through safe line-by-line reading with ReadAllLinesAsync. And example four demonstrates fire-and-forget process launching with StartAndForget. Each example is complete and ready to adapt.
Architecture
The pull request adds three evaluation scenarios to validate the skill activates correctly. Scenario one tests Process dot RunAndCaptureTextAsync on a .NET eleven target and asserts the API is present without manual redirection boilerplate. Scenario two validates the KillOnParentExit property. And scenario three is a negative case that ensures the skill doesn't activate for pre-.NET eleven code. These scenarios give us confidence the skill guidance fires at the right time.
Architecture
Finally, the skill is registered in the dotnet eleven plugin README. It's added to the skills list alongside the existing system-text-json skill, making it discoverable to anyone using the plugin. This is a simple one-line addition, but it's essential for the skill to appear in the plugin distribution.
PlainEnglish
The repository now includes a published skill guide for .NET 11 Process API improvements. Developers targeting .NET eleven will be able to discover guidance on deadlock-free process output capture, automatic child process cleanup, safe output reading without manual redirection boilerplate, and fire-and-forget process launching. The skill is registered in the dotnet eleven plugin directory and includes three evaluation scenarios to validate correct API usage.
CodeQuality
There's one documentation gap worth noting. SafeProcessHandle is mentioned in the 'When to Use' section as relevant for trimmer-friendly and NativeAOT-compatible process creation, but it never appears in the 'New APIs' section with a signature or example. This might be intentional if it's considered an advanced API, or it could be an oversight. It's worth confirming with the author whether SafeProcessHandle should be documented alongside the other APIs.
PlainEnglish
That's pull request eight sixty-six. It's a comprehensive skill guide documenting .NET 11 Process API improvements with practical examples and evaluation tests. There's one minor note about SafeProcessHandle being mentioned but not fully documented. The skill is registered in the dotnet eleven plugin and ready for distribution.
How this was made
Lenzon read dotnet/skills at pull request #866 and generated this walkthrough automatically. The narration above is the transcript of what it says.
Explain a pull request from your own repo
Point Lenzon at a repo or a pull request and get a narrated walkthrough like this one.
Try it