csharp-docs

Guides writing XML documentation comments for C# types and members.

Updated Aug 24, 2026
One-click install
npx skills add https://github.com/aggutierrez98/TP-TD --skill csharp-docs-aggutierrez98
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: csharp-docs
Source: https://github.com/aggutierrez98/TP-TD/tree/main/.agents/skills/csharp-docs
Command: npx skills add https://github.com/aggutierrez98/TP-TD --skill csharp-docs-aggutierrez98

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent or missing XML documentation comments make C# APIs hard to understand and maintain. This Skill provides clear conventions for documenting classes, methods, properties, and constructors so your codebase stays readable and professional. ## Core Features & Use Cases - XML Comment Conventions: Standardized guidance for <summary>, <remarks>, <param>, <returns>, <see>, and <example> tags on public and internal APIs. - Member-Specific Rules: Covers wording patterns for methods, constructors, properties, Boolean values, enums, out parameters, and exceptions. - Use Case: When reviewing a pull request that adds a new public method, use this Skill to verify the <param> descriptions are noun phrases, Boolean returns follow the "true if...; otherwise, false" pattern, and thrown exceptions are documented with <exception cref>. ## Quick Start Review the XML documentation comments on this C# class and rewrite them following the csharp-docs best practices.

Frequently Asked Questions about csharp-docs

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

FAQPage Schema
How do I write XML documentation comments in C#?▼

Use <summary> for a one-sentence description starting with a present-tense third-person verb, <param> for each parameter as a noun phrase, and <returns> for the return value. Add <remarks> for implementation details and <example> with <code> for usage samples.

How should I document C# method parameters with XML comments?▼

Write <param> descriptions as noun phrases beginning with an introductory article, without stating the data type. Boolean parameters use "true to ...; otherwise, false", and out parameters start with "When this method returns, contains ...".

Should internal C# members have XML documentation?▼

Public members should always be documented with XML comments. Documenting internal members is encouraged, especially when they are complex or not self-explanatory, to help future maintainers understand the code.

When should I use inheritdoc in C# documentation?▼

Use <inheritdoc/> to inherit documentation from base classes or interfaces when the member behaves the same. If there is a major behavior change, document the differences explicitly instead of inheriting.

How do I document exceptions thrown by C# methods?▼

Use <exception cref> for each exception thrown directly by the member, stating the condition under which it is thrown without phrases like "Thrown if". For nested members, document only exceptions users are most likely to encounter.