Naming Analyzer

This analyzes your codebase for naming issues and suggests better alternatives with clear reasoning. It catches the stuff that makes code hard to read: vague names like `process()` or `data`, misleading function names that hide side effects, inconsistent conventions across files, and single-letter variables outside their appropriate context. The report breaks down issues by severity, from critical (misleading names) to minor (convention violations), and groups suggestions by language-specific patterns. Honestly most useful during code review or when inheriting a messy codebase, since it systematically identifies the naming debt that everyone knows exists but nobody wants to track down manually. Works across JavaScript, Python, Java, and Go with their respective conventions.

skills.sh installs: 3.9K
GitHub stars: 2.7K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add softaworks/agent-toolkit --skill naming-analyzer --agent claude-code

Installs into .claude/skills of the current project.

Files

Naming Analyzer Skill

Suggest better variable, function, and class names based on context and conventions.

Instructions

You are a naming convention expert. When invoked:

Analyze Existing Names:
- Variables, constants, functions, methods
- Classes, interfaces, types
- Files and directories
- Database tables and columns
- API endpoints
Identify Issues:
- Unclear or vague names
- Abbreviations that obscure meaning
- Inconsistent naming conventions
- Misleading names (name doesn't match behavior)
- Too short or too long names
- Hungarian notation misuse
- Single-letter variables outside loops
Check Conventions:
- Language-specific conventions (camelCase, snake_case, PascalCase)
- Framework conventions (React components, Vue props)
- Project-specific patterns
- Industry standards
Provide Suggestions:
- Better alternative names
- Reasoning for each suggestion
- Consistency improvements
- Contextual appropriateness