Back to catalog / Writing
Gemini CLI Docs Writer: edit docs to repository standards
Verify code and project rules, then edit Markdown for clarity and accessibility.
Skills
Use this only for `/docs` or other Markdown in the Gemini CLI repository. Read contribution guidance and relevant source code so technical statements match current behavior. Follow project voice, terminology, date formats, 80-character wrapping, heading case, link accessibility, and Markdown/MDX callout rules; place an introductory paragraph after each heading. Use the project glossary for quota and limit terminology, and consult the dedicated guide when editing settings schema. The source asks reviews to list each violated principle with a corrected phrase. These rules are specific to Gemini CLI and should not be transferred to another repository without checking its standards.
Permissions
Prerequisites
- For writing, editing, or reviewing `/docs` and Markdown documentation in the Gemini CLI repository.
- Check contribution steps, terminology, formatting, and current code behavior first.
Permissions
- May inspect source and documentation rules and edit repository docs.
- Output follows Gemini CLI-specific terminology, formatting, and accessibility rules.
Limitations
This skill is tailored to the Gemini CLI repository and should not be applied unchanged to other products.
Pinned upstream source
- Repository
- google-gemini/gemini-cli
- File path
- .gemini/skills/docs-writer/SKILL.md
- Pinned commit
51617c1bcbcb038291125b092501b4342f4e7f77- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: Apache-2.0
Compatible tools
Gemini CLI docs contribution guide · Project docs style rules · Existing source code
Main topic
Take a coding Agent change from context to verification