Back to catalog / Writing
Gemini CLI string reviewer: check copy against project terminology
Review user-visible terms, tone, error guidance, and setting descriptions.
Skills
When reviewing Gemini CLI UI strings or user-facing prompts, open the project word list and the relevant focused guide first. Check that terminology matches code behavior, sentences are direct, errors offer one useful recovery path, setting copy follows its dedicated guidance, and terms such as quota and limit follow project definitions. For factual or operational guidance, inspect the settings schema and code path instead of inferring behavior from wording. The source requires concise numbered findings with the problematic phrase and a corrected version. This review is specific to Gemini CLI and does not establish terminology for another product.
Permissions
Prerequisites
- For localization review of Gemini CLI UI copy, setting descriptions, and user-visible strings.
- Read the project word list, quota-limit, settings, and error-message rules first.
Permissions
- May inspect source and existing strings, then propose targeted wording edits.
- The source asks for numbered findings with the incorrect phrase and a replacement.
Limitations
Terminology and product naming are specific to Gemini CLI; verify functional claims against code, not wording rules alone.
Pinned upstream source
- Repository
- google-gemini/gemini-cli
- File path
- .gemini/skills/string-reviewer/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 string guidelines · settings guidelines · source code and word list
Main topic
Take a coding Agent change from context to verification