docs-writer

Markdown documentation consistency is enforced by applying project standards for tone and formatting during the review process. This ensures all files align with contribution guidelines, reducing ambiguity and rework.

Reviewing docs against a CONTRIBUTING.md file involves cross-referencing changes with the latest codebase updates. This ensures feature documentation accurately reflects current project guidelines and maintains proper links to contribution standards.

Updating repository documentation involves reviewing existing Markdown files and proposing edits that reflect new features. Enforcing project standards during this process ensures accuracy and consistency across the /docs directory.

This documentation review process is tailored for the Gemini CLI project. It applies to creating and refining Markdown files within the /docs directory and repository MD files, enforcing references to the project's specific CONTRIBUTING.md guidelines.

The Gemini CLI documentation process streamlines review and editing by proposing aligned edits, but finalizing changes requires applying these proposals. It ensures all modifications follow project standards and tone before you merge the documentation updates.