Naming Format

This is the kind of thing you run when your codebase has userProfile.tsx sitting next to user-profile.tsx and nobody can agree on kebab versus camel. It scans your project to detect the dominant convention, audits everything against five high-impact rules (case consistency, file suffixes, export naming, index files, framework conventions), then fixes violations using git mv so you keep history. The workflow is straightforward: detect patterns, report violations by severity, apply fixes and update imports. Most useful during code reviews or when onboarding a team that inherited inconsistent naming. It won't make architectural decisions for you, but it will stop the bikeshedding about whether test files should end in .test or .spec.

Install to Claude Code

npx -y skills add tartinerlabs/skills --skill naming-format --agent claude-code