File Name Wizard
Run a systematic filename and naming-convention audit against AGENTS.md and implicit repo patterns before refactors or release review.
Overview
File Name Wizard is an agent skill most often used in Ship (also Build, Operate) that audits filenames and naming conventions against AGENTS.md and repo-wide patterns.
Install
npx skills add https://github.com/cygnusfear/agent-skills --skill file-name-wizardWhat is this skill?
- Two-phase workflow: discovery & standard extraction, then systematic per-file audit
- Reads root and nested AGENTS.md to extract explicit naming rules
- Glob-driven inventory of source, config, docs, and test files with a tracked todo list
- Infers implicit directory-level patterns when AGENTS.md is silent
- Covers component, utility, test, config, and constant/enum naming expectations
- Two-phase audit: discovery & standard extraction, then systematic file audit
Adoption & trust: 1.2k installs on skills.sh; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have AGENTS.md guidance and a growing tree of files, but no single pass that proves every path and basename actually follows those rules.
Who is it for?
Repos with AGENTS.md (or emerging conventions) where an agent should enumerate every file and report naming debt before a large rename or ship checkpoint.
Skip if: Greenfield projects with no files yet, or teams that only need runtime lint rules in ESLint without a full-repo filename inventory.
When should I use this skill?
User asks to check naming conventions, audit filenames, find naming inconsistencies, or validate file naming patterns.
What do I get? / Deliverables
You get a structured audit of naming violations and implicit-pattern gaps you can fix before merge or refactor, without renaming files automatically.
- Comprehensive file audit backlog
- Naming violation and anti-pattern report keyed to AGENTS.md and implicit rules
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Ship → review because the skill’s outcome is a consistency report and violation list on an existing codebase, aligned with pre-release quality gates. Review subphase fits checklist-driven audits (glob all files, extract standards, per-file pass/fail) rather than writing new product code.
Where it fits
Run a pre-merge audit so PRs do not introduce new basename styles that contradict AGENTS.md.
After adding directory-level AGENTS.md rules, verify existing files still match before documenting the layout for collaborators.
Quarterly hygiene pass to catch test and config filenames that diverged from dominant `*.test.ts` or `*.config` patterns.
How it compares
Use instead of spot-checking a few folders in chat when you need AGENTS.md-aligned, whole-tree filename coverage.
Common Questions / FAQ
Who is file-name-wizard for?
Solo and indie builders (and small teams) maintaining TypeScript/JavaScript-heavy codebases who document agent rules in AGENTS.md and want a repeatable naming audit.
When should I use file-name-wizard?
During Ship review before a release, during Build when standardizing a new module layout, or during Operate iterate when onboarding contributors and catching naming drift across source, test, config, and docs files.
Is file-name-wizard safe to install?
Treat it like any third-party agent skill: review the Security Audits panel on this Prism page and confirm the skill only reads and reports before you run it on production repos.
SKILL.md
READMESKILL.md - File Name Wizard
# 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 `AGENTS.md` files in the repository: - Root `AGENTS.md` if exists - Directory-specific `AGENTS.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 AGENTS.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 AGENTS.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., `index2.ts`, `common.ts`) - Dated names (e.g., `old-*.ts`, `legacy-*.ts`) - Feature flag names (e.g., `*-new.ts`, `*-enhanced.ts`) **Organizational Issues**: - File in wrong directory - Missing grouping suffix (e.g., should be `*.service.ts`) - Inconsistent with sibling files #### Step 4: Check File Contents Read the file to verify: - Does filename accurately describe contents? - Would a better name exist based on what's inside? - Are there naming conventions violations inside (class names, etc.)? #### Step 5: Record Findings Store in memory: ``` File: path/to/filename.ts Convention Used: camelCase Should Be: kebab-case Pattern: Violates directory convention Issues: - [Specific issue] Suggested Name: [better-name.ts] Severity: [HIGH|MEDIUM|LOW] ``` #### Step 6: Update Todo Mark file as audited in todo list. ### Phase 3: Pattern Analysis After auditing all files: #### Step 1: Identify Systemic Issues - Which directories have most inconsistencies? - What naming patterns are most violated? - Are there clusters of similar violations? #### Step 2: Find Outliers - Files that don't match any pattern - One-off naming schemes - Orphaned file types #### Step 3: Detect Missing Standards - Directories lacking clear naming conventions - File types without established patterns - Areas needing AGENTS.md documentation ### Phase 4: Generate Report Create a tk ticket tagged `audit` with the report as its body. Use `todos_oneshot(title: "Audit: Naming conventions", description: "<report content>", tags: "audit", type: