Overview
.NET DocFX Digest Steward is for repositories where API documentation should read like something a developer would actually use, not just a build artifact that happens to compile. It covers the surfaces that usually drift first: namespace summaries, overwrite files, examples, extension-member documentation, and the verification steps that prove the docs still match the code.
The skill is intentionally persistent. Instead of stopping at one summary or one missing XML comment, it is designed to keep working through the documentation backlog until the requested surface is complete or a concrete blocker appears.
Concepts
- Purpose-first documentation: the skill favors “why and when would I use this?” before dumping member inventories.
- Overwrite-aware maintenance: DocFX overwrite files, namespace pages, and examples are treated as first-class content, not optional polish.
- Verification is part of authorship: documentation is not considered done until the relevant build or quality checks have been exercised.
- Public-surface focus: the skill is most valuable when a .NET API changed and the docs must stay discoverable, navigable, and honest.
Usage guidance
Reach for this skill when a .NET library ships with DocFX and the documentation surface now lags behind the code. It fits repo-wide documentation audits, targeted namespace work, example backfilling, and overwrite-file upkeep after public API changes.
It works best when you want the agent to own the documentation loop end to end: inspect the API, update the prose, keep the doc structure coherent, and verify the result instead of leaving the last mile to manual cleanup.