sf-message-grammar-auditlisted

Audit user-facing messages in a Salesforce managed package for grammatical issues and generate a prioritized remediation report. Extracts messages from Apex classes, Apex triggers, LWC, Aura Components, Visualforce Pages, and Visualforce Components — same extraction as sf-message-catalog — then runs each through grammar analysis to flag article errors, subject-verb agreement, plural/singular mismatches, spelling, capitalization, punctuation, and cross-component wording inconsistencies. Produces a .docx report with current message, issue, suggested fix, component reference, and priority. Use when the user mentions 'grammar audit', 'message quality', 'fix error messages', 'grammatical issues', 'proofread messages', 'message consistency', 'clean up error messages', 'improve error messages', or asks to review messages for grammar, spelling, or consistency. Also triggers on 'typos in our messages' or 'message style review'. Internal-facing; can be scheduled monthly.
kugamon/salesforce-isv-skills · ★ 2 · Data & Documents · score 73

Install: claude install-skill kugamon/salesforce-isv-skills

# Salesforce Managed Package — Message Grammar Audit Generate an internal remediation report identifying grammatical issues in user-facing messages across a Salesforce managed package. This skill builds on the same extraction pipeline as `sf-message-catalog` but adds a grammar analysis pass and produces a different output format focused on actionable fixes. ## Before You Begin 1. **Read the docx skill** — locate and read the `docx` SKILL.md in your available skills. You will generate a .docx using docx-js. 2. **Check if a recent message catalog exists.** If the user has already run `sf-message-catalog` and the output is available, you can read that file to extract messages instead of re-querying Salesforce. Ask the user. 3. **If no catalog exists**, follow the same extraction process as `sf-message-catalog` (query Tooling API across all five component types). The extraction instructions are identical — refer to that skill for the full Tooling API query patterns and message-detection regex. 4. **Identify the Salesforce org connector.** Ask the user which connected Salesforce org to query. Look for available MCP tools matching `mcp__salesforce-*__tooling_execute`. If multiple orgs are connected, ask the user to pick one. 5. **Identify the managed package namespace prefix** (e.g., `kugo2p`). ## Phase 1: Extract All Messages Follow the same five-type extraction as `sf-message-catalog`: 1. **Apex Classes + Triggers** — `addError()`, `ApexPages.addMessage()`, `throw new ...Ex