api-docs

To write XML API documentation for SkiaSharp, you create and edit XML doc files for types, namespaces, and members within the docs/SkiaSharpAPI directory. You then run validation workflows to enforce .NET formatting and cross-reference guidelines for consistency.

Validating cross-references in SkiaSharp XML docs involves running the skill's documented validation commands on your files in the docs/SkiaSharpAPI directory. This workflow checks XML syntax, formatting, and <see> references to ensure compliance with .NET guidelines.

Yes, the workflow explicitly enforces .NET documentation guidelines for SkiaSharp. It reviews and edits your XML docs to ensure proper <see> references, consistent formatting, and compliance with established Microsoft patterns across the API surface.

You can review and edit existing SkiaSharp API docs by modifying the XML files in docs/SkiaSharpAPI. Running the validation workflow afterwards identifies syntax errors and cross-reference issues, ensuring your edits align with .NET documentation patterns.

SkiaSharp XML documentation fails validation when files in docs/SkiaSharpAPI contain incorrect XML syntax, broken cross-references, or formatting that violates .NET guidelines. Running the validation command isolates these specific errors for correction.

You need to run validation commands for SkiaSharp API documentation after editing or creating XML files in docs/SkiaSharpAPI. This ensures your documentation maintains consistent syntax, valid cross-references, and compliance with .NET guidelines before integration.