accelint-ts-documentation

You can audit JSDoc tags by scanning exported and internal code to validate the presence and consistency of @param, @returns, @template, @throws, and @example tags, then generating a structured report with actionable fixes for missing or misplaced documentation.

Comment quality checks involve scanning for marker usage like TODO, FIXME, HACK, and NOTE, identifying dead code comments, and verifying optimal comment placement to ensure internal utilities and public APIs remain clear and maintainable.

Documenting deprecated APIs and overloads requires applying judgment frameworks and decision trees to resolve conflicts, ensuring @deprecated tags and overload signatures are placed correctly while preserving existing tool directives.

Yes, you can generate a structured improvement plan by auditing the target codebase for JSDoc completeness and comment consistency, which produces an actionable report detailing required fixes for public APIs and internal utilities.

TypeScript documentation auditing applies to both exported public APIs and internal code, validating JSDoc tag completeness, marker usage, and comment placement across the entire codebase to ensure consistency regardless of visibility.