lens-docs

What problem does it solve?

LENS service documentation frequently falls out of sync with evolving source code, leading to inaccurate endpoint details, stale enum values, and missing DTO field information that causes integration errors and wastes developer time.

Core Features & Use Cases

• Multi-action documentation management: Supports reviewing existing docs for accuracy, creating new doc hubs for LENS services, updating docs after source code changes, and running full sync workflows to resolve all discrepancies.
• Automated source code validation: Extracts API endpoints, enum values, DTO fields, and auth policies directly from .NET or React/TypeScript source repos to cross-check against documentation.
• Enghub DocFX compliance: Generates and validates documentation following the standard enghub structure including index pages, API guides, onboarding content, and architecture overviews.
• Use Case: A developer working on the CMS LENS service can use this skill to automatically identify that a new workflowStage field was added to the CreateCaseRequest DTO in source code but is missing from the API guide, and generate the corrected documentation content.

Quick Start

Use the lens-docs skill to review the LEAPI service documentation for accuracy against its latest source code.