docs-writer

To keep repository documentation accurate, you can update existing markdown files, add new entity documentation, and perform staleness checks to ensure technical writing matches the current codebase state.

Generating changelog entries involves analyzing git history to automatically create markdown summaries of codebase updates, ensuring repository maintenance records reflect recent project changes accurately.

The best way to update README tables is to automatically modify the relevant markdown structures, adding new entity documentation to ensure the project documentation accurately reflects the newly added components.

Yes, you can proofread technical writing in markdown files to verify language consistency, tone, and technical accuracy, ensuring repository documentation maintains high quality and standards.

Checking documentation staleness involves scanning markdown files to identify outdated information, verifying that existing technical writing remains consistent with the current repository architecture and codebase.

Yes, the docs-writer skill explains repository architecture by referencing specific instruction and reference files to generate accurate technical documentation within markdown files.