docs-writer

To enforce documentation consistency, you can apply automated editing and reviewing to Markdown files, aligning content with project style guides and contribution guidelines to maintain uniform terminology and formatting.

Reviewing Markdown files for style guide compliance involves checking content against predefined contribution guidelines, ensuring terminology and formatting match project standards before updates are applied to the docs directory.

Editing Gemini CLI documentation to meet project standards requires applying structured reviews that reference the CONTRIBUTING.md and style guides, ensuring all Markdown content aligns with repository-specific formatting and terminology rules.

Yes, you can standardize Markdown writing for new features by supplying templates and checklists to contributors and editors, ensuring high-quality, standards-compliant documentation updates across the repository.

Structured checklists for contributing documentation are needed when updating the docs site or adding new features, ensuring that all edits produce high-quality, standards-compliant content aligned with project guidelines.

Documentation editing should reference the CONTRIBUTING.md file to ensure alignment with project standards, as it provides the necessary style guidance and terminology rules required for high-quality, consistent Markdown content.