Analyze unclear software names and produce context-aware replacements.
npx skills add https://github.com/hylarucoder/hai-stack --skill hai-naming
Please help me install this Agent Skill. Skill: hai-naming Source: https://github.com/hylarucoder/hai-stack/tree/main/skills/hai-naming Command: npx skills add https://github.com/hylarucoder/hai-stack --skill hai-naming
This Skill solves the problem of confusing, vague, or misleading names that make software concepts harder to understand, maintain, and evolve.
Ask the hai-naming skill to review the names in this module and recommend clearer replacements based on the system context.
High-intent search queries and answers about installing and using this skill.
Code review naming analysis evaluates unclear names across concepts, responsibilities, call flows, and boundaries to produce context-aware replacements. It generates a structured naming path to make decisions transparent and preserve system vocabulary.
Architecture-aware naming reviews assess domain entities by analyzing responsibility boundaries and caller viewpoints. They produce prioritized rename suggestions with migration scope to ensure names align with system architecture and domain modeling.
API design naming analysis applies a three-stage process: research-stage, first-principles, and final-after-reading. It evaluates API names against system vocabulary and caller viewpoints to generate replacements that clarify responsibility boundaries and endpoint contracts.
Module refactoring naming reviews cover variables, functions, files, and abstractions. They analyze unclear names within module boundaries and produce prioritized replacements with migration scope to maintain system vocabulary and responsibility separation.
Structured naming analysis is needed when product concepts or events affect system understanding and evolution. It analyzes names through research, first-principles, and final stages to ensure they preserve vocabulary and support migration planning.
Yes, naming analysis explicitly preserves system vocabulary and responsibility boundaries. It evaluates unclear names against existing concepts and caller viewpoints before generating context-aware replacements with migration considerations.
barrydobsonRename code elements to reflect domain semantics and avoid implementation details.
proven-xyzRename Python identifiers to improve readability during refactors.
robconeryAudit code against styleguide and glossary checklists for consistency.
CyranoBDetect and run project-native linters and type checkers to fix code issues.
