Underscore Naming Convention

Enforce snake_case naming for files, directories, and identifiers.

1|Updated Nov 26, 2025
One-click install
npx skills add https://github.com/Baneeishaque/ai-agents --skill underscore-naming-convention
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Underscore Naming Convention
Source: https://github.com/Baneeishaque/ai-agents/tree/main/.agents/skills/underscore_naming
Command: npx skills add https://github.com/Baneeishaque/ai-agents --skill underscore-naming-convention

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enforces a strict underscore_based naming convention for all project files, directories, and identifiers, eliminating inconsistencies and potential build issues.

Core Features & Use Cases

  • Violation Detection: Identifies files, directories, and identifiers that do not adhere to the snake_case convention.
  • Exemption Handling: Recognizes and respects industry-standard exempt names (e.g., azure-pipelines.yml, docker-compose.yml).
  • Full Blast Radius Tracing: Locates all references to a name before renaming to prevent broken links or imports.
  • Atomic Renaming: Executes renames and updates all cross-references atomically, ensuring code integrity.
  • Verification: Confirms zero stale references remain after the renaming process.
  • Use Case: When starting a new project or onboarding a new developer, apply this skill to ensure all code, configurations, and documentation consistently use snake_case, preventing future maintenance headaches.

Quick Start

Apply the underscore naming convention skill to enforce snake_case for all project files and directories.

Frequently Asked Questions about Underscore Naming Convention

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce snake_case naming conventions across my project files and directories?

To enforce snake_case naming conventions, this Skill detects violations in files, directories, and identifiers, traces all cross-references, and executes atomic renames using git mv. It verifies that zero stale references remain after the process.

How does file renaming handle cross-references to prevent broken imports?

File renaming handles cross-references by tracing the full blast radius of a name before executing changes. It performs atomic renames and updates all located references to verify zero stale links remain.

Do I need Git and a specific shell to run snake_case refactoring?

Yes, you need Git, write access to the repository, and either PowerShell 5.1+ or Bash 4+ to run snake_case refactoring. These dependencies are required to execute the atomic renames and trace cross-references.

What's the best way to batch rename files to snake_case without breaking builds?

The best way to batch rename files to snake_case without breaking builds is using a Skill that traces all references first, executes atomic git mv renames, and confirms zero stale imports remain to ensure code integrity.