Will It Vibe?Inconsistent route path casing within a file
Part of Architecture & Best Practices, which counts for 15% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
The same router file registers some routes with camelCase segments (/getUserData) and others with kebab-case or snake_case (/user-data, /user_data). Callers cannot guess the convention, generated clients and documentation read as inconsistent, and it usually reflects several people extending the file without a shared style. This is a naming-consistency heuristic, not a functional bug.
Why it matters
When one route file mixes /getUserData and /user-data, callers cannot predict the naming convention for the next endpoint without checking the source, and any client SDK generated from the routes inherits the same inconsistency. It usually means the file grew under several contributors without an agreed style, and new routes copy whichever nearby example the author happened to see first, compounding the inconsistency over time.
How to fix it
Pick one convention (kebab-case is the most common for URL paths) and document it briefly at the top of the router file or in a contributing guide. Rename the outlier routes to match, keeping the old paths as redirects or aliases for a deprecation window if external clients depend on them.
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