documentation

The Skill generates API docs by reading your source files to document individual endpoints or function signatures, providing concise parameter descriptions, return values, and examples while highlighting any ambiguities needing manual review.

Yes, you can apply this to single files within a repository. It reads the specific source file, detects the language-specific documentation format, and matches the existing project style before generating the required documentation and a list of modified files.

It ensures style matching by reading your source files and detecting existing language-specific documentation formats. It then applies these detected conventions to produce README sections, installation guides, and usage examples that align with your project.

The best way to document function signatures is using a verification process that re-reads the code to confirm parameter names, types, and return behavior, ensuring the generated API docs are accurate and highlighting ambiguities for manual review.

Yes, it supports generating GoDoc and Rustdoc comments. The Skill detects language-specific documentation formats across your codebase and applies the appropriate inline comment style to match your project's existing conventions.