## Summary The `glab` CLI documentation style guide ([`doc/development/documentation/cli_styleguide.md`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/development/documentation/cli_styleguide.md)) defines conventions for writing and reviewing CLI reference documentation. This issue tracks the work to make the `gitlab-org/cli` project aware of that style guide, by surfacing its conventions at the right moments: at the point of authoring, at review time, and when agents generate or review CLI documentation. ## Changes - `CONTRIBUTING.md`: Clarify the existing guidance on documentation MRs to explain that `docs/source/` files are auto-generated and must not be edited directly. Add a new "Documenting commands" section pointing contributors to the style guide. - `.gitlab/merge_request_templates/Documentation.md`: Add a pre-merge checklist covering the most common documentation issues: short description conventions, synopsis requirements, experimental and beta feature handling (command-level and flag-level cases), flag descriptions, and examples. - `AGENTS.md`: Add a "Documentation conventions" section so agents are aware of the key rules when generating or reviewing CLI documentation, with a link to the full style guide. - `.gitlab/duo/mr-review-instructions.yaml`: Add a new `Command documentation` block scoped to `internal/commands/**/*.go` so that Duo code review surfaces documentation issues at the source, where CLI documentation content is authored. ## Related - Parent issue: https://gitlab.com/gitlab-org/gitlab/-/work_items/596327 - Style guide MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/230899