document

Generate XML doc comments, READMEs, and OpenAPI descriptions from .NET source code.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/dimsour/dotnet-ai-toolkit --skill document-dimsour
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: document
Source: https://github.com/dimsour/dotnet-ai-toolkit/tree/main/plugins/dotnet-copilot/skills/document
Command: npx skills add https://github.com/dimsour/dotnet-ai-toolkit --skill document-dimsour

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The need for accurate, up-to-date documentation is essential in software development. Manually keeping documentation in sync with code can be time-consuming and prone to errors.

Core Features & Use Cases

  • Documentation Generation: Automatically generates XML doc comments, README files, architecture documents, and OpenAPI descriptions from code.
  • Code as Source of Truth: Ensures that all documentation is derived directly from the codebase, avoiding discrepancies.
  • Formats Supported: Generates documentation in various formats including XML Doc Comments, README sections, Architecture Documents, and OpenAPI descriptions.
  • Integration: Seamlessly integrates into existing workflows with commands like dotnet:document.

Quick Start

Use the dotnet:document command followed by the target file, directory, or topic to generate documentation.

Frequently Asked Questions about document

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

FAQPage Schema
How do I generate XML doc comments from my .NET source code?

To generate XML doc comments from .NET source code, you can use the `dotnet:document` command targeting specific files or directories to automatically derive documentation directly from your codebase.

Can I automatically create an OpenAPI description from code annotations?

Yes, you can automatically create OpenAPI descriptions from code annotations by running the documentation generation command, which ensures your API specifications stay synchronized with the source code.

What is the best way to keep README files synchronized with a .NET codebase?

The best way to keep README files synchronized with a .NET codebase is using a documentation generation tool that treats code as the source of truth, automatically updating README sections based on code changes.

Does this documentation generation approach work for architecture documents too?

Yes, this documentation generation approach works for architecture documents too, automatically extracting structural information from your codebase to maintain consistent and accurate architectural overviews.

How do I update existing documentation when my .NET code changes?

You update existing documentation when your .NET code changes by re-running the `dotnet:document` command, which regenerates and updates XML doc comments, READMEs, and OpenAPI descriptions based on the latest source code.