naming-analyzer

Analyze source code identifiers for naming convention violations across JavaScript, TypeScript, Python, Java, and Go.

Updated Jul 24, 2026
One-click install
npx skills add https://github.com/imMamdouhaboammar/kaku-chatgpt-harness --skill naming-analyzer-immamdouhaboammar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: naming-analyzer
Source: https://github.com/imMamdouhaboammar/kaku-chatgpt-harness/tree/main/.agents/skills/naming-analyzer
Command: npx skills add https://github.com/imMamdouhaboammar/kaku-chatgpt-harness --skill naming-analyzer-immamdouhaboammar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses technical debt caused by poor naming conventions, vague identifiers, and inconsistent coding styles that hinder readability and maintainability.

Core Features & Use Cases

  • Automated Analysis: Scans variables, functions, classes, and files for clarity, convention adherence, and potential bugs.
  • Severity Classification: Categorizes issues into Critical (misleading), Major (unclear), and Minor (convention violations).
  • Refactoring Support: Provides actionable suggestions and can generate scripts to apply renaming changes across a codebase.

Quick Start

Invoke the naming-analyzer skill on your src directory to receive a comprehensive report of all naming issues and suggested improvements.

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 source code for naming convention violations and unclear identifiers?

You can analyze source code identifiers to detect naming convention violations, misleading labels, and vague terminology, categorizing issues by severity to ensure clean code and reduce technical debt across your codebase.

Does static analysis for naming conventions work across multiple programming languages?

Static analysis for naming conventions operates across multiple programming languages, specifically supporting JavaScript, TypeScript, Python, Java, and Go to enforce industry-standard naming patterns consistently.

What is the best way to classify code review issues found during naming analysis?

The best way to classify code review issues found during naming analysis is by severity: Critical for misleading labels, Major for unclear identifiers, and Minor for convention violations, enabling targeted technical debt reduction.

Can I automatically generate refactoring scripts to fix vague variable names?

Yes, you can automatically generate refactoring scripts to fix vague variable names by receiving actionable suggestions during the analysis, allowing you to apply renaming changes across the entire codebase.

How do I run an automated code quality assessment on my src directory?

To run an automated code quality assessment on your src directory, invoke the naming analyzer to receive a comprehensive report detailing all naming issues, convention violations, and suggested improvements.