Naming Format

What it does

This skill automatically analyzes a project's codebase to identify and correct naming inconsistencies, ensuring adherence to defined conventions. It scans for dominant casing patterns, framework indicators (like Next.js or Expo), existing suffix patterns, and export naming styles. The skill then audits files against pre-defined rules and offers automated fixes like renaming files using git mv and updating import paths.

When to use it

• To enforce consistent naming conventions across a large codebase.
• When onboarding new developers to ensure they follow project standards.
• As part of an automated code review process to catch naming violations early.
• To standardize file suffixes (e.g., .test.ts vs .spec.ts).
• To improve the overall readability and maintainability of a project by adhering to framework conventions.

Key capabilities

• Detects dominant filename casing conventions.
• Identifies frameworks used in the project based on package.json.
• Analyzes existing suffix patterns.
• Audits code against rules for case consistency, file suffixes, export naming, and index files.
• Reports violations grouped by severity (HIGH, MEDIUM).
• Applies fixes including renaming files with git mv and updating import paths.

Example prompts

• "Run a naming audit on the current project."
• "Show me the high-severity naming violations."
• "Apply fixes for all case consistency issues."
• “What framework conventions are being used in this project?”

Tips & gotchas

• The skill relies on individual rule files located in the rules/ directory, which contain detailed explanations and examples.
• Review the audit results carefully before applying fixes to ensure accuracy.
• The skill uses git mv for renaming, preserving git history; however, it's still recommended to review changes after automated fixes.