csharp-docs

Document public C# types with XML comments and enforce XML tag usage.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that C# types are documented with XML comments and follow best practices for documentation.

Core Features & Use Cases

  • XML comment guidance for public members and internal members.
  • Templates and guidelines to maintain consistency across types, methods, properties, and parameters.
  • Use Case: A team migrating a .NET library adds XML summaries to public APIs and generates API docs for consumer projects.

Quick Start

Annotate a sample public class with XML comments and apply the summary and remarks guidelines to generate consistent API documentation.

Frequently Asked Questions about csharp-docs

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

FAQPage Schema
How do I generate consistent XML documentation for C# public types?

To generate consistent C# XML documentation, apply standardized XML comments to public types, methods, and properties using summary, remarks, see, and code example tags to enforce consistent API documentation across projects.

What is the best way to document C# methods and parameters for an API?

The best way to document C# methods and parameters is using XML comments with summary, remarks, and code example tags. This provides templates and guidelines to maintain consistency across types, methods, and parameters.

When do I need XML comments in C# code?

You need XML comments in C# code when you want to generate standardized API docs for consumer projects. Documenting all public C# types ensures consistent API documentation and best practices for teams migrating .NET libraries.

Does this approach support internal members or only public C# types?

This XML documentation approach provides guidance for both public members and internal members. It applies guidelines to methods, properties, parameters, and type members to maintain consistency across the entire codebase.

What XML tags should I use for C# code documentation?

You should use the summary, remarks, see, and code example XML tags for C# code documentation. Enforcing this specific tag usage ensures standardized docs are generated from the codebase with consistent API references.