docs-writer

To enforce consistent formatting and voice in markdown documentation, this Skill reviews and edits .md files to align content with specific project standards for grammar, tone, and structural guidelines.

Yes, you can update technical documentation when build processes change by directing the Skill to write or revise installation guides and content within the /docs directory to reflect recent updates.

The best way to review existing markdown files for content standards compliance is to run this Skill, which evaluates clarity, grammar, voice, tone, and formatting against established project guidelines.

This documentation writer primarily targets and enforces standards within the /docs directory, but it also processes and edits any .md files found throughout the repository.

To write new technical documentation sections matching current standards, the Skill generates content creation outputs that strictly adhere to your established voice, tone, language, and formatting rules.

A limitation of automated editing for technical communication is that the Skill relies on predefined project-specific standards, meaning it enforces existing guidelines rather than independently creating new documentation strategies.