naming-analyzer — Claude Code skill: variable naming audit
Reviews variable, function, class and file names for clarity, spots misleading labels and offers alternatives that follow language conventions.
npx claude-code-templates@latest --skill productivity/naming-analyzerWhat naming-analyzer does
The skill scans code for naming problems: overly generic terms (data, temp), misleading labels (a getUser function that mutates state), unclear abbreviations (usrCfg), booleans without prefixes (active instead of isActive). For each issue it provides a specific explanation and a better alternative. Checks variables, constants, methods, interfaces, database tables and API paths.
Recognises conventions for JavaScript, TypeScript, Python, Java and Go: camelCase for variables, PascalCase for classes, UPPER_SNAKE_CASE for constants. Separates critical errors (a name that does not match behaviour) from minor lapses (inconsistent casing). The report groups findings by priority and points to exact locations in the project.
Mention the skill in a prompt to run it. Works on the whole project, a folder or a single file.
What it helps with
- audit variable and function names for clarity
- spot boolean variables missing
is,hasorcanprefixes - identify functions whose names hide side effects
- align names with language conventions
- replace magic numbers with named constants
Example prompts for the agent
- Check names in
src/services/UserService.js— thegetUserfunction updateslastLogin, which is misleading - Review variable names in
src/utils, lots of single letters and abbreviations - Find boolean fields without prefixes in models and suggest corrected versions
How to install naming-analyzer
1claude-code-templates
npx claude-code-templates@latest --skill productivity/naming-analyzer2Skills CLI (Vercel)
npx skills add davila7/claude-code-templates --skill naming-analyzer -a claude-code3Manually: put the files in place
~/.claude/skills/naming-analyzer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/naming-analyzer/
Manually: put the files in place
.agents/skills/naming-analyzer/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/naming-analyzer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install davila7/claude-code-templates naming-analyzer2Manually: put the files in place
.github/skills/naming-analyzer/SKILL.mdPlatform CLI
gemini skills install https://github.com/davila7/claude-code-templates --path cli-tool/components/skills/productivity/naming-analyzerManually: put the files in place
.devin/skills/naming-analyzer/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about naming-analyzer
How to install naming-analyzer in Claude Code?
Run npx claude-code-templates@latest --skill productivity/naming-analyzer or npx skills add davila7/claude-code-templates --skill naming-analyzer -a claude-code, the skill file will appear in ~/.claude/skills/naming-analyzer/SKILL.md.
What does naming-analyzer do?
Analyses names in code — variables, functions, classes, files — and flags unclear, misleading or convention-violating labels. Suggests a corrected version with an explanation for each problem.
Which languages does naming-analyzer support?
JavaScript, TypeScript, Python, Java and Go. The skill recognises standard conventions for these languages: camelCase, PascalCase, snake_case and boolean prefixes.