check-naming

Analyze source files to identify poorly named identifiers and suggest replacements.

1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/mattbobambrose/mattbobambrose-claude-skills --skill check-naming
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-naming
Source: https://github.com/mattbobambrose/mattbobambrose-claude-skills/tree/main/plugins/code-quality/skills/check-naming
Command: npx skills add https://github.com/mattbobambrose/mattbobambrose-claude-skills --skill check-naming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill finds poorly named variables, functions, parameters, and other identifiers across source files to improve code clarity, reduce misunderstandings, and lower the risk of bugs caused by ambiguous names.

Core Features & Use Cases

  • Identify single-letter, overly short, overly long, misleading, generic, or inconsistent identifier names while respecting language idioms and conventions.
  • Scope analysis to a single file, a package/directory, or the entire project and produce a grouped report with file paths, line numbers, problems, and suggested replacements.
  • Use case: run across a codebase before a refactor to create a prioritized list of naming improvements for reviewers or automated refactoring tools.

Quick Start

Analyze the project for unclear or inconsistent identifier names and return a grouped report of file paths, line numbers, the issue, and suggested replacements.

Frequently Asked Questions about check-naming

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

FAQPage Schema
How do I find poorly named variables and functions in my source code?

To find poorly named variables and functions in source code, this Skill analyzes project files to identify single-letter, overly short, misleading, or generic identifiers. It outputs a grouped report with file paths, line numbers, issue types, and suggested replacement names.

Can I scan for inconsistent identifier names in a single file instead of the entire project?

Yes, you can scan for inconsistent identifier names in a single file. The analysis scope is flexible and can be applied to a single file, a specific package or directory, or the entire project, returning grouped findings based on the selected scope.

Does the naming analysis exclude generated and vendor code?

Yes, the naming analysis excludes generated and vendor code. It uses language-specific glob patterns to read project source files while automatically filtering out generated directories and vendor dependencies to focus on your own codebase.

What is static analysis for code readability and when should I use it?

Static analysis for code readability identifies ambiguous identifiers to reduce misunderstandings and lower bug risks. Use it before a refactor to generate a prioritized list of naming improvements for reviewers or automated refactoring tools.

What are the limitations of automated naming analysis for different programming languages?

Automated naming analysis respects language idioms and conventions but relies on glob patterns to find files. It identifies naming issues like overly long or inconsistent names, but does not refactor the code directly, only suggesting replacements for manual review.