wshaddix/dotnet-skills/dotnet-api-docs
Claude Code and agent skill by wshaddix/dotnet-skills
- community
- ext:[{"type":"template","description":"Custom templates for code generation"}]
Checking that the SKILL.md file is still in the repository.
Generating API documentation. DocFX setup, OpenAPI-as-docs, doc-code sync, versioned docs.
Install
npx vskill@latest install wshaddix/dotnet-skills/dotnet-api-docsSemi-extensibleMentions customization, but needs skill-specific knowledge. Read the extensible skills standard
SKILL.md
dotnet-api-docs
API documentation generation for .NET projects: DocFX setup for API reference from assemblies (docfx.json configuration, metadata extraction, template customization, cross-referencing), OpenAPI spec as living API documentation (Scalar and Swagger UI embedding, versioned OpenAPI documents), documentation-code synchronization (CI validation with -warnaserror:CS1591, broken link detection, automated doc builds on PR), API changelog patterns (breaking change documentation, migration guides, deprecated API tracking), and versioned API documentation (version selectors, multi-version maintenance, URL patterns).
Version assumptions: DocFX v2.x (community-maintained). OpenAPI 3.x via Microsoft.AspNetCore.OpenApi (.NET 9+ built-in). Scalar UI for modern OpenAPI visualization. .NET 8.0+ baseline for code examples.
Scope boundary: This skill owns API documentation generation from code -- the tooling and processes that turn source code, XML comments, and OpenAPI specs into browsable documentation. XML documentation comment syntax and authoring conventions are owned by [skill:dotnet-xml-docs]. OpenAPI specification generation and Swashbuckle migration are owned by [skill:dotnet-openapi]. CI/CD deployment of documentation sites is owned by [skill:dotnet-gha-deploy]. Documentation platform selection (Starlight vs DocFX vs Docusaurus) is owned by [skill:dotnet-documentation-strategy].
Out of scope: XML documentation comment syntax and authoring -- see [skill:dotnet-xml-docs]. OpenAPI spec generation and configuration (Swashbuckle, Microsoft.AspNetCore.OpenApi setup) -- see [skill:dotnet-openapi]. CI/CD deployment pipelines for documentation sites -- see [skill:dotnet-gha-deploy]. Documentation platform selection and initial setup -- see [skill:dotnet-documentation-strategy]. Changelog generation tooling and SemVer versioning -- see [skill:dotnet-release-management].
Cross-references: [skill:dotnet-xml-docs] for XML doc comment authoring, [skill:dotnet-openapi] for OpenAPI generation, [skill:dotnet-gha-deploy] for doc site deployment pipelines, [skill:dotnet-documentation-strategy] for platform selection, [skill:dotnet-release-management] for changelog tooling and versioning.
DocFX Setup for .NET API Reference
DocFX generates API reference documentation directly from .NET assemblies and XML documentation comments. It is the only documentation tool with native docfx metadata extraction from .NET projects.
Installation
Configuration (docfx.json)
Metadata Extraction
The metadata section controls how DocFX extracts API information from .NET projects:
Key metadata configuration options:
| Property | Purpose | Default | |
|---|---|---|---|
src.files | Project files to extract from | Required | |
dest | Output directory for YAML | api | |
properties.TargetFramework | TFM to build against | Project default | |
disableGitFeatures | Skip git blame info | false | |
filter | Path to API filter YAML | None (all public APIs) |
API Filtering
Exclude internal types from the generated documentation:
Reference the filter in docfx.json:
Template Customization
DocFX supports template overrides for custom branding:
Reference custom templates in docfx.json:
Cross-Referencing Between Pages
DocFX supports uid-based cross-references between API pages and conceptual articles:
OpenAPI Spec as Documentation
Generated OpenAPI specifications serve as living API documentation that stays in sync with the code. This section covers using OpenAPI output as documentation; for OpenAPI generation and configuration, see [skill:dotnet-openapi].
Scalar UI Embedding
Scalar provides a modern, interactive API documentation viewer:
Scalar renders the OpenAPI spec as an interactive documentation page with:
- Endpoint grouping by tags
- Request/response examples
- Authentication configuration
- "Try it" functionality for testing endpoints
Swagger UI Embedding
For projects using Swashbuckle or requiring the classic Swagger UI:
Versioned OpenAPI Documents
Serve multiple OpenAPI documents for different API versions:
Exporting OpenAPI for Static Documentation
Export the OpenAPI spec at build time for use in static documentation sites:
Alternatively, use the Microsoft.Extensions.ApiDescription.Server package to generate at build time:
For OpenAPI generation setup and Swashbuckle migration details, see [skill:dotnet-openapi].
Doc Site Generation from XML Comments
XML Docs to DocFX (Static HTML)
The primary pipeline for library API reference documentation:
For XML documentation comment authoring best practices, see [skill:dotnet-xml-docs].
XML Docs to Starlight (via Markdown Extraction)
For projects using Starlight instead of DocFX, extract API documentation as Markdown:
- Generate the XML doc file with
<GenerateDocumentationFile>true</GenerateDocumentationFile> - Use a conversion tool to transform XML docs to Markdown pages:
xmldoc2md(community tool): converts XML doc files to Markdown- Custom script: parse the XML file and generate Markdown pages for each type
- Include in Starlight build:
Configure the sidebar to auto-generate from the reference directory:
Keeping Docs in Sync with Code
CI Validation of Doc Completeness
Enforce XML documentation completeness in CI by treating CS1591 as an error:
This fails the build if any public member is missing XML documentation. Use the IsPublicLibrary condition (or per-project configuration) to apply only to published NuGet packages, not test projects or internal tools.
Broken Link Detection
Validate documentation links in CI:
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/dotnet-api-docs/SKILL.md
Popularity
- Repository stars
- 1
- 7-day trend score
- 3
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 18 Mar 2026, 7 months ago.
Extension points
templateCustom templates for code generation
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/wshaddix/dotnet-skills/dotnet-api-docs)