Guide developers to choose clear, intent-revealing names for code.
npx skills add https://github.com/onesyntax/skills --skill naming-onesyntax
Please help me install this Agent Skill. Skill: naming Source: https://github.com/onesyntax/skills/tree/main/skills/naming Command: npx skills add https://github.com/onesyntax/skills --skill naming-onesyntax
This skill guides developers to choose names that clearly reveal intent and avoid cryptic abbreviations and noisy prefixes, reducing maintenance overhead and confusion.
Rename unclear identifiers in a sample snippet to clearer alternatives. For example, replace pcguda with a descriptive noun or verb phrase representing its purpose, replace gwd with a pronounceable name, and replace m_configIssues with a descriptive, non-prefixed variable.
High-intent search queries and answers about installing and using this skill.
The best way to choose intent-revealing names is to replace cryptic abbreviations with descriptive noun or verb phrases. This skill enforces Uncle Bob's principles to guide you toward clear, pronounceable names that reduce maintenance overhead and confusion.
To refactor unclear identifiers for code readability, replace cryptic strings like 'pcguda' with descriptive nouns and remove noisy prefixes like 'm_'. This skill provides concrete alternatives and rationale to ensure your refactored names are pronounceable and searchable.
Yes, clean code naming guidance applies across multiple programming languages. This skill helps you implement intent-revealing names for classes, functions, and variables during implementation, code review, and refactoring regardless of your specific tech stack.
You should avoid encodings and prefixes because they create noisy, unpronounceable names that hinder collaboration. This skill guides you to strip prefixes like 'm_' and replace them with descriptive, intent-revealing names to improve code review clarity.
Yes, you can get concrete alternatives for abbreviations during code review. This skill analyzes identifiers like 'gwd' and provides specific, pronounceable replacements with explanations to ensure your codebase remains consistent and maintainable.
JeroenJochemsAnalyze and improve code naming conventions across programming languages.
marcioaltoeStandardize file, directory, class, function, and variable naming across a codebase.
Chang-Shih-YungAggregate type checker, linter, and test results into a 0-10 composite score.
evancaApply Effective Dart guidelines to enforce idiomatic Dart and Flutter code standards.
