.agents/skills/api-docs/references/checklist.md
Based on official .NET API documentation guidelines.
Classify issues by severity when reviewing documentation.
Issues that damage credibility or break functionality:
<, >, &; missing closing tags; mismatched tag namesIssues that violate standards or leave gaps:
<value />, <summary />, <returns />, or <summary></summary> with only whitespace (note: <remarks /> is acceptable)<see langword> for true/false/nullStyle improvements that enhance quality:
<paramref> when referring to parameters<remarks> that would add valueWhen reporting issues, organize by severity and include:
### CRITICAL
- **File**: `docs/SkiaSharpAPI/SkiaSharp/SKPaint.xml`
- **Issue**: Spelling error "recieve"
- **Current**: `<summary>Recieve the paint data.</summary>`
- **Fix**: `<summary>Receives the paint data.</summary>`
### IMPORTANT
- **File**: `docs/SkiaSharpAPI/SkiaSharp/SKCanvas.xml`
- **Member**: `DrawRect`
- **Issue**: Empty param tag
- **Current**: `<param name="rect" />`
- **Fix**: `<param name="rect">The rectangle to draw.</param>`
End reviews with: