skills.rest
mikecubed
mikecubedCOMMUNITY
Explore all skills by this author →
GitHub

naming-check

Enforce NAME-1 through NAME-7 naming rules across Go, TypeScript, Python, JavaScript, and Rust codebases.

Updated Mar 18, 2026
Search Tags:#quality#standards#multi-language#conventions#static-analysis#lint#naming
One-click install
npx skills add https://github.com/mikecubed/agent-orchestration --skill naming-check
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: naming-check
Source: https://github.com/mikecubed/agent-orchestration/tree/main/plugins/ccc/skills/naming-check
Command: npx skills add https://github.com/mikecubed/agent-orchestration --skill naming-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

In multi-language codebases, naming inconsistencies cause confusion, reduce readability, and slow down reviews. This Skill enforces NAME-1 through NAME-7 rules to ensure identifiers convey intent across languages.

Core Features & Use Cases

  • Checks for meaningful, descriptive names and flags obvious anti-patterns (NAME-1).
  • Enforces boolean predicates with proper prefixes (NAME-2) across languages.
  • Detects misleading names and inconsistent domain terminology (NAME-3 to NAME-6).
  • Validates test function naming patterns (NAME-7) in supported languages and guides refactoring.
  • Loads language-specific conventions from references/{language}.md to tailor rules per language.

Quick Start

Run naming-check on your repository to enforce language-specific naming conventions and consistency.

Frequently Asked Questions about naming-check

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

FAQPage Schema
How do I enforce consistent naming conventions across multi-language codebases?▼

You can enforce consistent naming conventions across multi-language codebases by applying NAME-1 through NAME-7 rules to flag meaningless names and inconsistent domain terminology in identifiers.

Does static analysis for naming conventions support Go, TypeScript, Python, JavaScript, and Rust?▼

Yes, static analysis for naming conventions supports Go, TypeScript, Python, JavaScript, and Rust projects, loading language-specific references to guide casing and evaluation.

How do I check boolean predicates and test function naming patterns in my code?▼

To check boolean predicates and test function naming patterns, the NAME-2 and NAME-7 rules validate proper boolean prefixes and test function structures, guiding refactoring where needed.

What is the best way to detect misleading names and inconsistent domain terminology in APIs?▼

The best way to detect misleading names and inconsistent domain terminology in APIs is by applying NAME-3 through NAME-6 rules during static analysis to ensure identifiers convey intent.

Why do I need language-specific references for linting identifier names?▼

Language-specific references for linting identifier names are needed to tailor casing and naming conventions to the unique syntax rules of Go, TypeScript, Python, JavaScript, and Rust.

When should I not use automated naming checks for code review?▼

Automated naming checks for code review should not be used as the sole quality gate when domain-specific terminology requires contextual judgment beyond static rule enforcement.

Related Skills

Explore More Software Engineering Skills→
DaRacciDaRacci
18

code-style

Enforce repository-specific Nix code style guidelines with formatting and naming conventions.

Community
Basic
flpbaladaflpbalada
280

naming-cheatsheet

Apply the A/HC/LC naming pattern to variables, functions, and class names.

Community
Basic
CloakingGhostCloakingGhost

qa-agent

Automate code review, error fixing, and structural improvements via static analysis.

Community
Intermediate
D0NMEGAD0NMEGA
8

plankton-code-quality

Automate formatting and linting on file edits via PostToolUse hooks.

Community
Advanced