file-name-wizard
Systematic audit of filenames and naming conventions against AGENTS.md standards and codebase patterns.
- Discovers all source, config, documentation, and test files, then extracts explicit naming rules from AGENTS.md files and identifies implicit patterns within each directory
- Analyzes each file for convention violations (wrong case, mixed patterns, missing suffixes), clarity issues (vague or misleading names), and anti-patterns (temporary names, version suffixes, generic names)
- Identifies systemic issues across directories, detects outliers, and flags missing naming standards that should be documented
- Generates a structured audit report categorized by severity and directory, with statistics on violation types and recommendations for each problematic file
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
More from cygnusfear/agent-skills
architectural-analysis
Deep architectural audit focused on finding dead code, duplicated functionality, architectural anti-patterns, type confusion, and code smells. Use when user asks for architectural analysis, find dead code, identify duplication, or assess codebase health.
34video-explorer
This skill should be used when analyzing video files. You cannot process video directly, so this skill extracts frames hierarchically - starting with a quick overview, then zooming into regions of interest with higher resolution and temporal density. Use when asked to watch, analyze, review, or understand video content.
34review-changes
Code review of current git changes, compare to related plan if exists, identify bad engineering, over-engineering, or suboptimal solutions. Use when user asks to review changes, check git diff, validate implementation quality, or assess code changes.
33design-spec-extraction
Use when extracting design specifications from visual sources including Figma exports, UI mockups, screenshots, or live website captures. Produces W3C DTCG-compliant JSON with component trees for code generation and developer handoff.
32obsidian-plan-wiki
Create and manage behavior specification wikis in Obsidian format. Use when creating specs, documenting features, or when user mentions "wiki", "spec", "feature", or "Obsidian".
31update-docs
Update all documentation in docs and AGENTS.md files to match current codebase state. Use when user asks to update docs, refresh documentation, sync docs with code, or validate documentation accuracy.
31