naming-helper

Propose and audit code identifiers, APIs, and configuration keys against project conventions.

9|3|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill naming-helper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: naming-helper
Source: https://github.com/Sir-chawakorn/sanook-cli/tree/main/skills/naming-helper
Command: npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill naming-helper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates naming ambiguity and inconsistency in codebases by providing context-aware suggestions for identifiers, APIs, and configuration keys that align with existing project conventions.

Core Features & Use Cases

  • Convention Inference: Automatically detects existing case styles and domain vocabulary by scanning the surrounding codebase.
  • Quality Auditing: Evaluates proposed names against a strict quality bar to ensure they are intention-revealing, searchable, and free of noise words.
  • Use Case: When refactoring a module, use this Skill to ensure new function names match the existing verb register and cardinality patterns of sibling functions, preventing naming drift.

Quick Start

Ask the naming-helper to suggest a better name for the current function based on the existing naming conventions in this file.

Frequently Asked Questions about naming-helper

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

FAQPage Schema
How do I ensure consistent code identifiers when refactoring a module?

To ensure consistent code identifiers when refactoring, this Skill scans your local codebase to infer existing case styles and domain vocabulary. It then proposes new names that match the verb register and cardinality patterns of sibling functions, preventing naming drift.

What makes a clean code identifier intention-revealing and searchable?

An intention-revealing identifier clearly communicates its purpose without noise words. This Skill evaluates proposed names against a strict quality bar to ensure terminology is searchable, non-misleading, and perfectly aligned with your project's domain vocabulary.

How do I audit API names and configuration keys for naming clarity?

You can audit API names and configuration keys for clarity by applying this Skill's quality auditing feature. It validates proposed identifiers against a quality bar that prioritizes intention-revealing, searchable, and non-misleading terminology within your project.

Can I use naming conventions inference for an existing codebase with mixed case styles?

Yes, you can use this Skill on a codebase with mixed case styles. The convention inference mechanism operates by scanning the surrounding code to detect existing case styles and domain vocabulary, providing context-aware naming candidates that fit your local environment.

Does naming consistency checking require any external dependencies or setup?

No, naming consistency checking requires no external dependencies or setup. The Skill operates independently with no required components, directly inferring existing case styles and domain vocabulary from the local codebase to provide context-aware suggestions.

Why does my refactored code suffer from naming drift across sibling functions?

Naming drift occurs when new functions fail to match the existing verb register and cardinality patterns. This Skill prevents drift by inferring local codebase conventions and validating suggestions against a strict quality bar for intention-revealing, searchable terminology.