naming-convention-guard

Naming Convention Guard automatically enforces language-specific rules like camelCase for variables and functions, PascalCase for classes, and snake_case where appropriate. It triggers on code creation and edits, flagging violations and proposing corrections in real time across .ts, .tsx, .js, and .jsx files.

Yes. Naming Convention Guard supports language-specific naming rules for Python, Go, Java, and Kotlin projects. It applies appropriate conventions for each language—including proper constant naming and file naming patterns—and auto-triggers on writes and new declarations across .py, .go, .java, and .kt files.

The tool enforces camelCase for variables and functions, PascalCase for classes, snake_case for constants and module names, and grep-friendly conventions for searchability. It detects bad names during code creation and proposes improvements based on language-specific standards and readability best practices.

Consistent naming conventions reduce cognitive load during code review and refactoring, improve searchability with grep-friendly patterns, and prevent naming drift across team projects. Real-time enforcement during editing catches inconsistencies before they compound.

Naming Convention Guard primarily auto-triggers on code creation and edits. For existing code, it flags naming violations as you write or modify declarations, allowing incremental refactoring and enforcement of conventions on actively edited sections.

The tool monitors TypeScript, JavaScript, Python, Go, Java, and Kotlin source files. Supported extensions include .ts, .tsx, .js, .jsx, .py, .go, .java, and .kt, with language-specific conventions applied automatically.