string-reviewer

Reviews user-facing strings in codebases against clarity, brevity, and style guidelines.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/rameshkumarchouhanr/gemni-cli --skill string-reviewer-rameshkumarchouhanr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: string-reviewer
Source: https://github.com/rameshkumarchouhanr/gemni-cli/tree/main/.gemini/skills/string-reviewer
Command: npx skills add https://github.com/rameshkumarchouhanr/gemni-cli --skill string-reviewer-rameshkumarchouhanr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? User-facing text in a codebase often becomes inconsistent, verbose, or unclear over time. This Skill audits inline text, error messages, and UI strings against defined voice principles, terminology rules, and settings guidelines, producing structured suggestions without modifying code directly. ## Core Features & Use Cases - UX Writing Audit: Reviews strings against core voice principles such as deterministic clarity, front-loaded actionability, and agentic error recovery. - Terminology Enforcement: Checks strings against a project word list of preferred, discouraged, and cautionary terms. - Settings Schema Review: Applies noun-first labeling, positive boolean logic, and verb stripping rules when settingsSchema.ts is modified. - Use Case: After adding a new error message to the CLI, ask for a string review to receive a numbered list of violations with corrected phrasing, such as replacing "Please wait while loading" with a telemetry-style status under five words. ## Quick Start Ask Gemini to review the user-facing strings in the files you just changed and suggest improvements following the string reviewer guidelines.

Frequently Asked Questions about string-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review user-facing strings in my codebase?

Invoke the string-reviewer skill and point it at the files or changes containing UI text. It audits strings against voice principles like front-loaded actionability and the five-word status rule, then returns a numbered list of violations with corrected phrasing.

What makes a good error message in CLI tools?

A good error message pairs a human-readable explanation with exactly one recovery path, such as a command, link, or suggested prompt. It leads with the goal and action, avoids first-person pronouns, and places machine error codes after the plain-language explanation.

Does the string reviewer change my code automatically?

No, the skill only suggests changes and never rewrites strings without explicit user approval. It presents findings in a fixed list format showing the violated principle, the incorrect phrase, and the corrected phrase.

How are settings labels supposed to be written?

Settings labels follow noun-first labeling, positive boolean logic, and verb stripping. For example, "Disable auto update" becomes "Auto update", and "Enable prompt completion" becomes "Prompt completion", with boolean inversion handled in the config loader.

Which words should be avoided in UI text?

The word list prohibits terms like "etc.", "in order to", "log in", and "hostname", and flags "leverage", "e.g.", "i.e.", and "please" for cautious use. Preferred alternatives include "such as", "sign in", and "host name".