Naming Analyzer

This analyzes your codebase for naming issues and suggests better alternatives with clear reasoning. It catches the stuff that makes code hard to read: vague names like `process()` or `data`, misleading function names that hide side effects, inconsistent conventions across files, and single-letter variables outside their appropriate context. The report breaks down issues by severity, from critical (misleading names) to minor (convention violations), and groups suggestions by language-specific patterns. Honestly most useful during code review or when inheriting a messy codebase, since it systematically identifies the naming debt that everyone knows exists but nobody wants to track down manually. Works across JavaScript, Python, Java, and Go with their respective conventions.