Agent skill · writing content · aiskillstore
file-name-wizard
Audit all filename and naming conventions in the codebase against CLAUDE.md standards and common patterns. Use when user asks to check naming conventions, audit filenames, find naming inconsistencies, or validate file naming patterns.
Why this skill is useful
Adds a systematic approach to auditing filenames and naming conventions that the AI wouldn't reliably generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Filename & Naming Convention Audit Instructions Perform systematic audit of all filenames and naming conventions in the codebase to identify inconsistencies, anti-patterns, and violations of naming standards. Phase 1: Discovery & Standard Extraction Step 1: Find All Files Use Glob to identify all files in the codebase: Source files (.ts, .tsx, .js, .jsx, etc.) Config files Documentation files Test files Create comprehensive todo list of all files to audit. Step 2: Extract Naming Standards Read all CLAUDE.md files in the repository: Root CLAUDE.md if exists Directory-specific CLAUDE.md files Extract naming conventions: File naming patterns (kebab-case, PascalCase, etc.) Directory structure rules Component naming rules Utility/helper naming rules Test file naming rules Config file naming rules Constant/enum file naming rules Step 3: Identify Implicit Patterns Even without explicit CLAUDE.md rules, identify patterns: Most common naming convention in each directory Grouping patterns (e.g., .service.ts, .controller.ts) Organizational patterns (e.g., components/, utils/, lib/) Phase 2: Systematic File Audit For EACH file in the todo list: Step 1: Analyze Filename What is the current filename? What naming convention does it use? Is it descriptive and clear? Does it match its purpose/content? Step 2: Check Against Standards Compare to: Explicit CLAUDE.md rules for this directory Implicit patterns in the same directory Common naming conventions for file type Best practices for the framework/language Step 3: Identify Issues Naming Convention Violations: Wrong case (e.g., PascalCase when should be kebab-case) Mixed conventions (e.g., userAuth.service.ts mixing camelCase and dot notation) Inconsistent with directory pattern Clarity Issues: Vague names (e.g., utils.ts, helpers.ts, stuff.ts) Overly verbose names Misleading names (content doesn't match name) Abbreviations without context Anti-Patterns: Temporary names (e.g., temp.ts, test.ts, new-.ts, -v2.ts) Generic names (e.g., …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/file-name-wizard