naming-scan

Review code and configuration names for clarity, consistency, and intent.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/Objective-Arts/lens --skill naming-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: naming-scan
Source: https://github.com/Objective-Arts/lens/tree/main/workflow-skills/utils/naming-scan
Command: npx skills add https://github.com/Objective-Arts/lens --skill naming-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps ensure that names used in code and configuration are clear, consistent, and accurately reflect their intent, reducing ambiguity and improving maintainability.

Core Features & Use Cases

  • Clarity Review: Identifies jargon, ambiguity, and inconsistent naming patterns.
  • AI Antipattern Detection: Flags common AI-generated naming smells like enterprise suffixes and generic -er names.
  • Use Case: Before committing code, run this scan to catch unclear variable names like temp_data or inconsistent function naming like getUser and fetchUserData.

Quick Start

Run the naming-scan skill on the entire src directory.

Frequently Asked Questions about naming-scan

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

FAQPage Schema
How do I check variable and function names for code clarity and consistency?

To check code clarity, scan function, variable, class, file, and config key names against naming principles. This flags jargon, ambiguity, and inconsistent patterns to ensure names accurately reflect their intent.

What are common AI-generated naming antipatterns in code?

Common AI-generated naming antipatterns include generic -er names and unnecessary enterprise suffixes. Detecting these involves scanning for ambiguous terms and inconsistent patterns that reduce code maintainability.

Does naming convention review apply to configuration keys and API endpoints?

Naming convention review applies to configuration keys and API endpoints, alongside CLI commands, directories, and files. It checks for consistent patterns, scope-appropriate length, and meaningful suffix or prefix usage.

When do I need to scan for readability issues in my codebase?

You need to scan for readability issues before committing code to catch unclear variables like temp_data or inconsistent functions like getUser and fetchUserData. This prevents ambiguity and improves long-term maintainability.

What is the best way to detect jargon and unnecessary abbreviations in code?

The best way to detect jargon and unnecessary abbreviations is applying a naming scan that enforces clarity principles, verb and noun usage, and scope-appropriate length across all code and configuration names.