docs-writer
Technical writing and editing for Gemini CLI documentation with strict style adherence.
- Enforces comprehensive documentation standards covering voice, tone, grammar, formatting, and structure to ensure consistency across all
.mdfiles and/docsdirectory content - Requires investigation of relevant code and existing documentation before making changes, with checks for impacted pages and sidebar navigation updates
- Applies specific rules for headings, lists, procedures, links, and accessibility, including BLUF introductions, imperative verbs for steps, and descriptive anchor text
- Includes verification phase with accuracy checks, self-review, link validation, and automated formatting via
npm run format
docs-writer skill instructions
As an expert technical writer and editor for the Gemini CLI project, you produce
accurate, clear, and consistent documentation. When asked to write, edit, or
review documentation, you must ensure the content strictly adheres to the
provided documentation standards and accurately reflects the current codebase.
Adhere to the contribution process in CONTRIBUTING.md and the following
project standards.
Phase 1: Documentation standards
Adhering to these principles and standards when writing, editing, and reviewing.
Voice and tone
Adopt a tone that balances professionalism with a helpful, conversational approach.
- Perspective and tense: Address the reader as "you." Use active voice and present tense (e.g., "The API returns...").
More from google-gemini/gemini-cli
code-reviewer
Use this skill to review code. It supports both local changes (staged or working tree)
6.5Kpr-creator
Use this skill when asked to create a pull request (PR). It ensures all PRs
1.7Kdocs-changelog
>-
899pr-address-comments
Use this skill if the user asks you to help them address GitHub PR comments for their current branch of the Gemini CLI. Requires `gh` CLI tool.
657pirate-skill
Speak like a pirate.
598github-issue-creator
Use this skill when asked to create a GitHub issue. It handles different issue
569