string-reviewer

Reviews user-facing strings and UI text against clarity, brevity, and terminology style rules.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Inconsistent, verbose, or unclear user-facing strings degrade product quality and confuse users. This Skill audits inline text, error messages, and status updates in a codebase against a defined UX writing style guide, flagging violations without rewriting anything without approval. ## Core Features & Use Cases - UX Writing Audit: Reviews strings against core voice principles including deterministic clarity, front-loaded actionability, and agentic error recovery. - Terminology Enforcement: Checks wording against a project word list of preferred, prohibited, and cautionary terms. - Settings Label Review: Applies noun-first labeling, positive boolean logic, and verb stripping rules to settings schema labels and descriptions. - Use Case: After modifying packages/cli/src/config/settingsSchema.ts, ask for a string review to receive a numbered list of violations with corrected phrasing for each label and description. ## Quick Start Review the user-facing strings in my recent changes and suggest corrections following the project writing 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 for clarity?

Invoke the string review on your changed files to audit inline text, error messages, and status updates against UX writing rules. It returns a numbered list pairing each flagged phrase with a corrected version and the principle violated.

What writing rules does a UX string review enforce?

It enforces deterministic clarity, front-loaded action patterns, status updates under five words, active voice without first-person pronouns, and error messages paired with one recovery action. Terminology is checked against a project word list of preferred and prohibited terms.

Does the string reviewer change my code automatically?

No, it only suggests changes and never rewrites strings without explicit user approval. Each suggestion is presented in a structured list showing the incorrect phrase and the proposed correction.

How should settings labels be written for scannability?

Settings labels use noun-first labeling, positive boolean logic, and verb stripping. For example, "Disable auto update" becomes "Auto update", and "Enable prompt completion" becomes "Prompt completion".

When should I not use this string review approach?

It is designed for user-facing product text, not for reviewing code logic, documentation long-form content, or marketing copy. It also requires the project's word list and settings guidelines to apply its terminology rules accurately.