docs-writer

To ensure repository documentation follows contribution standards, enforce voice, tone, formatting, and structure conventions. Verify links, grammar, and clarity before finalizing edits to maintain consistency across all Markdown files.

Updating existing Markdown files requires verifying documentation claims against the latest relevant materials, primarily the codebase packages. This ensures the revised content accurately reflects current behavior before changes are finalized.

Drafting new technical documentation involves creating content in the /docs directory and Markdown files. It requires strict adherence to project documentation conventions, formatting rules, and contribution guidance to maintain consistency.

Yes, documentation editing requires strict link and consistency verification before finalizing changes. This process enforces naming conventions, checks grammar, and validates formatting to ensure accurate, standards-compliant writing.

Yes, you can review existing documentation pages for accuracy by performing standards-based reviews. This enforces voice, tone, and formatting rules while checking claims against the latest codebase materials.

You need to verify documentation claims against the codebase packages before finalizing any edits. This accuracy check ensures that updated content correctly reflects the latest behavior and implementation details.