file-name-wizard

Filename auditing systematically scans all files to identify naming inconsistencies, case violations, and anti-patterns like vague names (`utils.ts`, `temp.ts`). Run this skill to generate a structured report with per-file findings, violation categories, and remediation guidance for refactoring.

Extract explicit naming rules from `CLAUDE.md` files in your codebase, then identify implicit naming patterns within directories. This skill reads both sources to detect deviations, directory-specific rules, and cross-file mismatches so you can enforce consistent conventions.

Yes. The skill identifies clarity issues like generic names, misleading labels, and temporary file markers. It flags patterns that hinder discoverability and complicate onboarding, then outputs findings in a format compatible with downstream analysis and RAG tooling.

Run this skill as part of codebase reviews, refactors, and CI pipelines to detect pattern deviations during code changes. It generates embeddable structured output that feeds into automated workflows and keeps naming conventions aligned as your codebase evolves.

Inconsistent naming conventions reduce discoverability, confuse developers navigating unfamiliar code, and slow team ramp-up. Systematic auditing identifies these inconsistencies early so new members encounter predictable, standardized filenames that improve clarity and maintainability.

The skill produces a structured report including a per-file findings log, violation taxonomy, and remediation guidance. Output is formatted for integration with downstream analysis tools and RAG systems for actionable refactoring recommendations.