docs-writer

To update markdown documentation, inspect repository code to confirm examples and flags are correct, then revise the .md files to improve clarity and enforce the project's style guide.

Fix broken links in technical writing by checking and repairing cross-links within the markdown files. You should also update navigation entries like sidebars when adding or removing pages.

Ensure style consistency in CLI documentation by applying the project's style guide across all edited .md files, correcting formatting, tone, and structure during the documentation editing process.

Yes, you can verify markdown examples against repository code. The process involves inspecting the codebase to confirm that command examples, flags, and behaviors are accurate before updating docs.

Yes, you should run a formatting command after editing markdown files. The process suggests running the project's specific formatting command to ensure the updated documentation meets repository standards.

Adding new pages to CLI documentation involves authoring the content, verifying implementation details, enforcing the style guide, and updating navigation elements like sidebar entries to include the new page.