lens-docs

To validate API documentation against .NET source code, use an automated sync workflow that extracts endpoints, enum values, and DTO fields directly from the repository to cross-check against existing docs. This ensures documentation accuracy and structural compliance.

The best way to generate missing DocFX documentation for LENS services is to run a full sync workflow that follows the standard enghub DocFX structure. It validates endpoint coverage and automatically generates missing content for index pages, API guides, and architecture overviews.

Automated source code validation detects stale enum values by extracting current enum definitions directly from .NET or React/TypeScript source repositories and cross-checking them against the documented values. It flags discrepancies and generates detailed review reports.

Yes, you can update React TypeScript API docs automatically after source code changes by running a documentation update workflow. It extracts modified DTO fields and auth policies from the source repo to resolve discrepancies and generate corrected documentation content.

Yes, the lens-docs skill supports creating new documentation hubs for LENS services. It generates the required enghub DocFX structure, including onboarding content, API guides, and architecture overviews, ensuring full structural compliance from the start.

Endpoint coverage validation fails when DTO fields are added to source code because the documentation cross-check identifies the missing fields in the API guide. Running a full sync workflow resolves this by generating the corrected documentation content automatically.