skills.rest
RealEmmettS
RealEmmettSCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

naming-conventions

Enforce SHAUGHV naming conventions for code identifiers, files, Git branches, and migrations.

Updated May 20, 2026
Search Tags:#database#Git#naming conventions#code standards#SHAUGHV
One-click install
npx skills add https://github.com/RealEmmettS/shaughv-code --skill naming-conventions-realemmetts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: naming-conventions
Source: https://github.com/RealEmmettS/shaughv-code/tree/main/plugins/shaughv-code/skills/naming-conventions
Command: npx skills add https://github.com/RealEmmettS/shaughv-code --skill naming-conventions-realemmetts

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures consistent and clear naming conventions across SHAUGHV brand work, improving code readability, maintainability, and collaboration.

Core Features & Use Cases

  • Code Identifiers: Guidelines for naming variables, functions, classes, constants, and booleans.
  • Files & Folders: Rules for naming files and folders in SHAUGHV repositories.
  • Git: Conventions for naming repositories, branches, commits, pull requests, feature flags, and migrations.
  • Databases & Migrations: Naming standards for database columns and migration files.
  • Auditing: A procedure for auditing existing folders, repositories, or projects for naming compliance.
  • Use Case: When naming a new variable in a codebase or a new branch in a repository, use this Skill to ensure compliance with SHAUGHV naming conventions.

Quick Start

Use the naming-conventions skill to name a new variable. The skill will guide you through the appropriate naming conventions based on the variable's purpose.

Frequently Asked Questions about naming-conventions

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

FAQPage Schema
What naming conventions should I use for Git branches and commits?▼

Git branch and commit naming conventions follow specific SHAUGHV brand standards to improve repository readability. Reference files provide authoritative guidance on structuring branch names and commit messages for consistent version control collaboration.

How do I name database columns and migration files correctly?▼

Database migrations and columns require standardized naming to maintain schema clarity. This enforces specific naming standards for database columns and migration files, ensuring structural consistency across all database operations.

How do I audit an existing repository folder for naming compliance?▼

Auditing existing folders for naming compliance involves running a specific procedure to check repositories or projects against SHAUGHV standards. This evaluates code identifiers, files, and Git artifacts to identify deviations from the rules.

What are the rules for naming code identifiers like variables and functions?▼

Code identifiers like variables, functions, classes, constants, and booleans require specific naming patterns to ensure readability. The skill applies reference guidelines to enforce clear and consistent identifier names across the codebase.

Do I need to know SHAUGHV brand standards to use these code standards?▼

Yes, utilizing these naming conventions requires a comprehensive understanding of SHAUGHV brand standards and coding practices. The skill applies these specific brand rules to your code identifiers, files, and Git workflows.

Can I use this to name feature flags and pull requests?▼

Yes, feature flags and pull requests are covered by the Git naming conventions. The skill enforces specific naming rules for these artifacts, ensuring that feature toggles and PR titles align with SHAUGHV brand standards.

Related Skills

Explore More Software Engineering Skills→
cenmiaocenmiao

openspec-sp-git-worktree

Create isolated Git worktrees with branch naming and baseline tests.

Community
Intermediate
TheGreatLTheGreatL

fix

Automate code linting and formatting with Prettier and a linter before commits.

Community
Basic
edulazaroedulazaro
12

lc:slow-queries

Analyze Laravel Eloquent and Query Builder usage to detect database performance bottlenecks.

Community
Intermediate
EIS-ITSEIS-ITS

Global Coding Style

Enforce consistent naming, formatting, and DRY standards across codebases.

Official
Basic