Inconsistent variable naming convention
Part of Code Quality & Syntax, which counts for 20% of the overall score. When this check fires it deducts 2 points from that category, once per scan, no matter how many places it turns up.
What it detects
A single file mixes camelCase and snake_case for variable names.
Why it matters
Mixing camelCase and snake_case variables in the same file makes readers second-guess whether two names are different variables or one concept spelled twice, and typo bugs like userId versus user_id blend right in. It usually happens when API payload field names leak into local naming.
How to fix it
Standardize local variables and functions on camelCase for JS/TS, keeping snake_case only at the boundary where external data enters (API responses, database rows), and convert to camelCase fields in one mapping step at that boundary. Enforce it with ESLint's camelcase rule or @typescript-eslint/naming-convention.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo