source-code-documentation-rewrite

To fix documentation drift after renaming features, this Skill analyzes actual implementation files to rewrite outdated manuals. It resolves discrepancies by extracting current technical specifications directly from the source code, ensuring your project documentation remains a reliable source of truth.

To sync API reference documentation with evolving codebases, this Skill scans your repository source files and rewrites the relevant docs. It preserves your existing documentation structure while updating technical claims, method signatures, and error codes to match the new implementation.

Yes, this documentation rewrite approach preserves your existing manual's structure. It focuses on updating technical claims, method signatures, and error codes within the current layout rather than generating entirely new documents from scratch.

The best way to rewrite project manuals after a major codebase refactor is using source-driven updates. This approach systematically analyzes actual implementation files rather than relying on potentially stale existing text to ensure accurate technical writing.

Yes, you need read access to repository source files for code documentation synchronization. This access is required for the Skill to perform comparative analysis between existing documentation and the actual implementation files before generating content.