naming-analyzer

Analyze source code identifiers to enforce naming conventions across JavaScript, TypeScript, Python, Java, and Go.

9|2|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/stephanj/claude-code-collections --skill naming-analyzer-stephanj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: naming-analyzer
Source: https://github.com/stephanj/claude-code-collections/tree/main/skills/naming-analyzer
Command: npx skills add https://github.com/stephanj/claude-code-collections --skill naming-analyzer-stephanj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses technical debt caused by poor naming conventions, misleading identifiers, and inconsistent styles, which often lead to bugs and increased cognitive load for developers.

Core Features & Use Cases

  • Automated Convention Checking: Validates identifiers against language-specific standards for JavaScript, TypeScript, Python, Java, and Go.
  • Semantic Analysis: Detects misleading names that do not match actual function behavior and identifies vague or overly abbreviated variables.
  • Refactoring Support: Provides actionable suggestions and can generate scripts to standardize naming across an entire codebase.

Quick Start

Invoke the naming-analyzer skill to review the naming conventions and suggest improvements for the current file.

Frequently Asked Questions about naming-analyzer

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

FAQPage Schema
How do I automate code review for naming conventions in Python and Java?

Automated code review for naming conventions validates identifiers against language-specific standards for Python and Java to reduce technical debt. It targets variable, function, and class naming patterns to enforce consistency and prevent logic errors.

Can I detect misleading function names and vague variables during static analysis?

Static analysis detects misleading function names and vague variables using semantic analysis to check if names match actual behavior. This identifies overly abbreviated identifiers and reduces cognitive load for developers working across the codebase.

Does the naming analyzer support refactoring guidance for JavaScript and TypeScript?

The naming analyzer supports refactoring guidance for JavaScript and TypeScript by providing actionable suggestions to standardize naming. It can generate scripts to automatically correct inconsistent identifiers across the entire codebase.

What is the best way to enforce clean code naming standards across multiple programming languages?

Enforcing clean code naming standards across multiple programming languages requires analyzing source code identifiers against language-specific rules. This approach reduces inconsistent styles and technical debt while improving overall code readability.

Why does poor naming cause technical debt and how can I fix it?

Poor naming causes technical debt by introducing misleading identifiers and inconsistent styles that increase cognitive load and lead to bugs. You can fix it by analyzing source code to enforce naming conventions and applying actionable refactoring suggestions.

Can I use this for automated consistency enforcement in Go codebases?

Automated consistency enforcement in Go codebases validates identifiers against language-specific naming standards. It targets variable, function, class, and constant naming patterns to reduce technical debt and improve readability.