naming-discipline

Enforce consistent semantic naming conventions for code identifiers, Redis keys, and wire-level terms.

Updated Jun 15, 2026
One-click install
npx skills add https://github.com/tanghuo/th-skill --skill naming-discipline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: naming-discipline
Source: https://github.com/tanghuo/th-skill/tree/main/skills/naming-discipline
Command: npx skills add https://github.com/tanghuo/th-skill --skill naming-discipline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that names are consistent across your codebase, enhancing readability and maintainability.

Core Features & Use Cases

  • Consistent Naming: Enforces one naming shape per concept family.
  • Clear Semantics: Promotes clear domain, action, and ownership within names.
  • Refactoring Tool: Assists in refactoring names during code reviews or changes.

Quick Start

Review and refactor the naming discipline using the skill: naming-discipline review <file>.

Frequently Asked Questions about naming-discipline

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

FAQPage Schema
How do I enforce consistent naming conventions across my codebase during code reviews?

You can enforce consistent naming conventions by using a code review tool that checks all code identifiers against a structured semantic naming convention and provides automated refactoring suggestions for any violations found.

What is the best way to standardize Redis key naming patterns in my software development environment?

To standardize Redis key naming patterns, apply a semantic naming convention that enforces one consistent naming shape per concept family, ensuring clear domain, action, and ownership for all wire-level terms and database keys.

How do I refactor inconsistent code identifiers to improve code quality and readability?

Refactor inconsistent code identifiers by running an automated review tool that detects naming deviations and provides targeted refactoring suggestions to align all names with a unified semantic convention.

Does this naming convention tool work for both code variables and wire-level terms?

Yes, the naming convention tool works for both code variables and wire-level terms, ensuring that all code identifiers, Redis keys, and wire-level terms adhere to a consistent semantic naming convention.

When do I need to use a structured naming discipline for my software standards?

You need structured naming discipline when your codebase requires enhanced readability and maintainability, ensuring that every concept family maintains one consistent naming shape with clear domain and action semantics.

What are the limitations of using automated naming conventions for code reviews?

While automated naming conventions identify semantic deviations and suggest refactors, they require a structured software development environment to function and cannot contextualize naming choices outside of the defined convention guidelines.