Naming Convention Auditor for Contracts

WHAT IT DOES

This tool connects to your EVM wallet and audits smart contract naming conventions against configurable style patterns. It reads contract source code to identify functions, variables, constants, modifiers, events, and structs, then checks each name against the selected naming convention (Solidity standard camelCase, snake_case, or strict camelCase). The tool provides detailed reports with violations and suggested fixes, helping teams maintain consistent naming across their codebase.

HOW TO USE

Connect your Web3 wallet using the Connect button. Paste your contract source code in the Contract Source Code field. Select your preferred naming convention from the dropdown (Solidity Standard, Snake Case, or Strict camelCase). Click "Audit Naming" to analyze the source code. Click "Load Sample" to populate fields with an example contract containing various naming issues. Results appear in the Results card with a summary of names checked, violations found, and compliance status, followed by a detailed list of each violation with the name, type, message, and suggested fix.

TECHNICAL MECHANISM: NAMING CONVENTION ENFORCEMENT VIA PATTERN MATCHING

The tool uses regular expression pattern matching to identify all named entities in Solidity source code. It extracts function names, variable declarations, constants, event definitions, and struct definitions. For each extracted name, the tool checks it against the selected convention: camelCase (first letter lowercase, no underscores), snake_case (lowercase with underscores), or UPPER_CASE for constants. The tool also supports leading underscores for internal functions in Solidity standard mode. Each violation is categorized with the entity type, the expected pattern, and a concrete suggestion for remediation. The compliance status is calculated based on the number of violations.

WHAT IT CANNOT SEE

This tool cannot enforce naming conventions that are context-dependent or project-specific without configuration—the tool provides a baseline but cannot account for team-specific rules. It cannot detect naming violations in compiled bytecode or external dependencies—the tool only analyzes source code. It cannot automatically rename or fix identified issues—the tool only identifies problems. It relies on source code parsing and may produce false positives for complex patterns—some code may use non-standard but valid naming. It cannot verify semantic meaning or appropriateness of names beyond format compliance—the tool does not check whether names accurately describe their purpose.

PLEASE NOTE

This is a read-only tool—it never signs transactions. All data is processed in-memory and never persists. The tool supports EVM chains only—Ethereum, Polygon, BSC, Arbitrum, Optimism, Avalanche, Base, and Fantom. Naming conventions are project-specific—adapt the tool's rules to your team's preferences. The tool is a starting point for style review and should be complemented by code reviews and team discussions.