.NET DocFX Digest Steward

Description

Create and maintain developer-friendly DocFX documentation digests for .NET public APIs. Keep namespace pages, generated API pages, examples, availability notes, and verification aligned with the actual source code and tests.

Critical

• This skill is autonomous by default. If the user invokes it without naming a namespace, type, member, or changed API — including a bare direct skill call with no parsed arguments, a host-initiated continuation, or a host re-entry that invokes dotnet-docfx-digest directly with no extra arguments after the skill already auto-triggered — assume non-human/autonomous execution, treat the request as a repo-wide DocFX audit and repair task, and do not ask startup scoping or approval-to-continue questions.
• Resolve bundled scripts from the loaded dotnet-docfx-digest skill directory first. If that install path is unavailable and the target repository contains the repo-managed source copy, fall back to skills/dotnet-docfx-digest/scripts/*.cs. Do not claim the scripts are unavailable until both locations have been checked.
• docfx.cs is fast by default: a plain run validates Markdown, prose, DocFX overwrite layout, namespace pages, extension tables, and required examples without building, restoring, or running DocFX/gh. Use it freely during iteration — it discovers the public API from existing DocFX YAML metadata or a conservative source scan, and ends with a [processes] dotnet=0 msbuild=0 docfx=0 gh=0 summary. Compilation and network access are opt-in.
• Iterate quickly with the fast path, reading diagnostics as the next work queue:

dotnet run --file "<resolved-skill-dir>/scripts/docfx.cs" -- --repo-root "<repo-root>" --json

• Before claiming completion, run agents.cs, then a thorough build-backed verification that compiles samples, uses reflection-backed API discovery, and verifies the DocFX build: