naming-analyzer

Analyze code identifiers for clarity, convention compliance, and naming intent.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ceshez/VELAR --skill naming-analyzer-ceshez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: naming-analyzer
Source: https://github.com/ceshez/VELAR/tree/main/.agents/skills/naming-analyzer
Command: npx skills add https://github.com/ceshez/VELAR --skill naming-analyzer-ceshez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces technical debt caused by unclear, inconsistent, or misleading identifier names, making code harder to read, review, and maintain.

Core Features & Use Cases

  • Identifier analysis: Reviews variables, functions/methods, classes/types, files/directories, database tables/columns, and API endpoints.
  • Issue detection: Flags vague names, confusing abbreviations, convention violations, misleading names with hidden side effects, awkward lengths, and un-prefixed booleans.
  • Convention-aware recommendations: Suggests improved names aligned to language norms (e.g., camelCase/PascalCase/UPPER_SNAKE_CASE, boolean prefixes) and outputs a structured report with reasoning.
  • Refactoring support: Produces prioritized renaming guidance suitable for systematic cleanups across a codebase.

Quick Start

Ask the AI to analyze the naming in the directory src/ and return a structured report of critical, major, and minor naming issues with specific replacement suggestions.

Frequently Asked Questions about naming-analyzer

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

FAQPage Schema
How do I check my codebase for poor variable and function naming conventions?

You can analyze identifier naming by scanning targeted files or directories to detect vague names, confusing abbreviations, and convention violations. The process outputs a structured report with severity-classified findings and context-aware suggested replacement names aligned to language norms.

What is the best way to standardize boolean naming patterns across a heterogeneous TypeScript project?

Standardizing boolean naming requires analyzing identifiers for un-prefixed booleans and applying language-specific boolean naming guidance. This produces prioritized renaming guidance for systematically cleaning up inconsistent naming patterns across heterogeneous project files.

Does the identifier analysis detect misleading function names with hidden side effects?

Yes, identifier analysis detects misleading names with hidden side effects. It flags these issues during code review or refactoring planning scans, classifying them by severity and providing context-aware suggested names that accurately reflect the function's intent and behavior.

Can I use this for code review and refactoring planning on specific directories?

Yes, you can use this for code review and refactoring planning by running targeted file or directory scans. It identifies naming issues and outputs severity-classified findings with context-aware suggested names suitable for systematic codebase cleanups.

What types of identifiers are reviewed when checking code clarity and naming intent?

When checking code clarity and naming intent, the review covers variables, functions/methods, classes/types, files/directories, database tables/columns, and API endpoints. It assesses these identifiers for clarity, correctness of intent, and convention compliance.