Naming Convention Enforcer

What this skill does

Walks a repository's tree and flags files or directories whose names don't match the configured convention (kebab-case, camelCase, PascalCase, or per-directory rules). Produces a rename plan as a git mv script.

Inputs

• repo_dir: project root.
• rules: a YAML mapping path globs to expected convention. Example: 'src/components/**' -> PascalCase, 'src/utils/**' -> kebab-case.
• Optional extension_overrides: extensions to ignore (e.g., .md for prose-typed filenames).

Steps

1. Read rules and validate each glob. Deny rules with overlapping globs unless one explicitly extends the other.
2. Walk the repo respecting .gitignore (use git ls-files to enumerate tracked files only).
3. For each file/dir, match against the most specific rule.
4. Test the basename against the rule's regex:
   • kebab-case: ^[a-z0-9]+(-[a-z0-9]+)*\.(ext)?$.
   • camelCase: ^[a-z][a-zA-Z0-9]*(?:\.[a-z]+)?$.
   • PascalCase: ^[A-Z][a-zA-Z0-9]*(?:\.[a-z]+)?$.
5. For each mismatch, propose a rename: convert via tokens (split on case-boundaries and underscores/hyphens) and rejoin.
6. Detect collisions: if multiple files would rename to the same target, mark the group manual-resolution.
7. Generate a rename-plan.sh with git mv old new lines (one per file). Include a set -euo pipefail header and a follow-up git status reminder.
8. Generate a markdown report listing the rename plan grouped by directory.
9. Compute follow-up imports: for each rename of a JS/TS source, list the files that import it (rg -nN "from ['\"].*<basename>['\"]" src/) so consumers can update.

Output

rename-plan.sh (executable shell script), naming-report.md (per-directory summary), and naming-imports.md (downstream import sites needing update). Stdout prints mismatch count and collision count.

Verification

Apply rename-plan.sh on a feature branch and run the test suite plus typecheck; if any imports broke, the import-update step missed a reference. Re-walk the tree and confirm zero mismatches remain. Ensure the plan respects case-sensitivity quirks (macOS HFS+ default is case-insensitive; renames within case differences require a two-step rename).

Edge cases

• Files referenced by config (e.g., webpack.config.js expects specific names): exclude via extension_overrides or path glob.
• Test files paired with source (Foo.tsx <-> Foo.test.tsx): rename together; the plan should pair them.
• Generated files (schema.gen.ts): exclude unless explicitly opted-in.
• Vendor / third-party directories: skip; they aren't owned by this repo.