csharp-docs

Enforce XML documentation comments on public C# types and members.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/afonsoft/VideoChat --skill csharp-docs-afonsoft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: csharp-docs
Source: https://github.com/afonsoft/VideoChat/tree/main/.agents/skills/csharp-docs
Command: npx skills add https://github.com/afonsoft/VideoChat --skill csharp-docs-afonsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

C# projects often lack consistent, machine-readable documentation. This Skill ensures that public API members are documented with XML comments and encourages documenting complex internal members to improve maintainability and onboarding.

Core Features & Use Cases

  • Enforce XML comments on public types and members.
  • Encourage documenting internal members for clarity in complex code.
  • Provide guidance for XML tags like <summary>, <remarks>, and <see> to produce usable API docs.

Quick Start

Add XML documentation comments to a representative C# type and run your documentation linting tool to see results.

Frequently Asked Questions about csharp-docs

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

FAQPage Schema
How do I add XML documentation comments to public C# types and members?

To add XML documentation comments to C# code, you insert standard XML tags like <summary>, <remarks>, and <see> directly above public types and members to ensure consistent, machine-readable API documentation. This skill enforces that public members include these comments to improve maintainability and onboarding.

What is the best way to document internal C# members for complex code?

Documenting internal C# members is best done by applying XML comments when the internal logic is non-trivial. This skill encourages documenting complex internal members to provide clarity, ensuring that machine-readable docs accurately reflect intricate codebase behaviors for better maintainability.

Does this XML documentation skill work for C# libraries and services exposing public APIs?

Yes, this XML documentation skill is designed specifically for C# codebases that expose public APIs, including libraries and services. It enforces consistent XML comments on public types and members, ensuring that complex types and services produce usable, machine-readable API documentation.

Which XML tags should I use for C# API documentation?

For C# API documentation, you should use XML tags such as <summary>, <remarks>, and <see> to generate usable docs. This skill provides guidance on proper tag usage, ensuring that your codebase maintains machine-readable documentation standards across all exposed public types.

Why do I need XML comments in my C# project?

XML comments are needed in a C# project to generate machine-readable API documentation and improve code maintainability. Without consistent XML comments on public members, onboarding new developers becomes difficult, and automated documentation tools cannot parse your codebase effectively.

How do I check if my C# codebase meets XML documentation standards?

To check if your C# codebase meets XML documentation standards, you run a documentation linting tool against your code. This skill applies XML documentation best practices, allowing you to verify that public types and complex internal members have the required machine-readable comments.