naming-format — Claude Code skill: file naming and export audit
This skill audits file names, suffixes and export names across a project, then offers fixes. Handy for refactors and for reading unfamiliar repos.
npx skills add tartinerlabs/skills --skill naming-format -a claude-codeWhat naming-format does
The skill acts as a naming-convention auditor. It scans the project to find the dominant filename casing, checks suffix patterns such as .test.ts versus .spec.ts, and looks at how exports and index files are named. By default it only reports: each finding comes as path:line, a description of what is wrong, and the suggested fix. Findings are grouped under HIGH, MEDIUM and LOW, with a violation count per rule at the end.
The casing, suffix, export-naming and index-file rules are language-neutral, so they apply to any project. A separate framework rule set loads only when Next.js or Expo shows up in package.json. The skill runs on haiku and its tools are limited to Read, Glob, Grep, Edit and Bash(git:*).
Edits happen only when you ask for them. Then it renames files with git mv, updates import paths in dependent files, and verifies that no broken imports remain. A vague request gets a report first. Worth knowing before you run it: dynamic imports and string-based paths are easy to miss, so run your tests after a rename pass.
What it helps with
- spot files with mixed casing in one directory
- unify test suffixes across the repo
- check export names before publishing a package
- map the conventions of an unfamiliar codebase
- rename files and update the imports that point at them
Example prompts for the agent
- audit the file names in this project and show me where the conventions break
- rename the files in src/utils to one style and fix the imports
- check the exports in this package and tell me if the naming is consistent
How to install naming-format
1Skills CLI (Vercel)
npx skills add tartinerlabs/skills --skill naming-format -a claude-code2Manually: put the files in place
~/.claude/skills/naming-format/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/naming-format/
1Skills CLI (Vercel)
npx skills add tartinerlabs/skills --skill naming-format -a codex2Manually: put the files in place
.agents/skills/naming-format/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add tartinerlabs/skills --skill naming-format -a cursor2Manually: put the files in place
.cursor/skills/naming-format/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install tartinerlabs/skills naming-format2Manually: put the files in place
.github/skills/naming-format/SKILL.md1Skills CLI (Vercel)
npx skills add tartinerlabs/skills --skill naming-format -a gemini-cli2Platform CLI
gemini skills install https://github.com/tartinerlabs/skills --path plugins/quality/skills/naming-formatManually: put the files in place
.devin/skills/naming-format/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add tartinerlabs/skills --skill naming-format -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about naming-format
How do I install naming-format in Claude?
Run npx skills add tartinerlabs/skills --skill naming-format -a claude-code. The skill lands in ~/.claude/skills/naming-format/SKILL.md.
What does naming-format do?
It checks file names, suffixes, export names and index files against a consistent rule set. You get a report by default, and it applies fixes when you ask.
Which rules depend on the framework?
Casing, suffixes, exports and index files are checked everywhere. Framework rules load only when Next.js or Expo is detected in package.json.
Source text
SKILL.md · MIT
--- name: naming-format description: Use when reviewing file names, renaming files, fixing naming conventions, or auditing exports. Enforces consistent casing and suffix patterns. license: MIT allowed-tools: Read Glob Grep Edit Bash(git:*) model: haiku effort: medium compatibility: Any language project; casing/suffix/export rules are language-neutral, framework naming rules apply only when that framework is detected metadata: short-description: File naming and export conventions. --- You are a naming conventions expert. Audit and report by default; rename files or edit exports only when the user asks you to fix, rename, or standardise something. When the ask is unclear, report first and offer to apply the fixes. ## Rules Overview | Rule | Impact | File | |------|--------|------| | Case consistency | HIGH | `rules/case-consistency.md` | | File suffixes | HIGH | `rules/file-suffixes.md` | | Export naming | HIGH | `rules/export-naming.md` | | Index files | HIGH | `rules/index-files.md` | | Framework conventions | MEDIUM | `rules/framework-conventions.md` (only when a supported framework is detected) | ## Workflow ### Step 1: Detect Scan the project to identify: - Dominant filename casing convention (count files by pattern) - Framework indicators (e.g. Next.js/Expo in `package.json`) — used only to decide whether to load `rules/framework-conventions.md` - Existing suffix patterns (`.test.ts` vs `.spec.ts`, etc.) - Export naming patterns across the codebase The casing, suffix, export-naming, and index-file rules are language-neutral and always apply. Load `rules/framework-conventions.md` **only when a supported framework (Next.js / Expo) is detected**. ### Step 2: Audit Check all files and exports against the rules. Report each finding as `path:line` — what is wrong → the fix, grouped under `### HIGH` / `### MEDIUM` / `### LOW`, and close with a per-rule violation count. ### Step 3: Fix Apply fixes for each violation: 1. Rename files with `git mv` 2. Update all import paths in dependent files 3. Verify no broken imports remain after renames
© tartinerlabs · MIT · tartinerlabs/skills
