Naming format
Claude Code skills for git workflows, GitHub automation, security audits, code refactoring, and project tooling
npx -y skills add tartinerlabs/skills --skill naming-formatAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when reviewing file names, renaming files, fixing naming conventions, or auditing exports. Enforces consistent casing and suffix patterns.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.0 KB, as published. Nobody here has run it
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 loadrules/framework-conventions.md - Existing suffix patterns (
.test.tsvs.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:
- Rename files with
git mv - Update all import paths in dependent files
- Verify no broken imports remain after renames