From evolutionary-naming
Audits and improves poor code names via evolutionary process in audit or improve modes. Targets -Manager/-Util suffixes, single-letter vars, god methods.
npx claudepluginhub kawasima/evolutionary-naming --plugin evolutionary-namingThis skill is limited to using the following tools:
**Naming is a process, not a single step.** Names evolve through 7 progressive steps grouped into 3 phases. Match the depth of work to the user's actual story — don't run the full pipeline every time.
Suggests improved names for variables, functions, classes, files, DB tables, and API endpoints using language-specific conventions like camelCase or snake_case.
Suggests improved names for variables, functions, classes, files, DB tables, and API endpoints using language conventions like camelCase, snake_case, and prefixes for booleans.
Refactors working code into clean, readable, maintainable code using Robert C. Martin's Clean Code principles on names, functions, comments, formatting, and objects. For new code, PR reviews, legacy refactoring, team standards.
Share bugs, ideas, or general feedback.
Naming is a process, not a single step. Names evolve through 7 progressive steps grouped into 3 phases. Match the depth of work to the user's actual story — don't run the full pipeline every time.
Based on Arlo Belshee's "Naming as a Process" (CC BY 3.0). Updated edition: digdeeproots.com.
| Phase | Steps | Nature |
|---|---|---|
| Phase 1: Insight → Name | Missing → Nonsense → Honest → Honest and Complete | Universal. Pure naming. No structural change. Safe to walk continuously. |
| Phase 2: Name → Structure | Honest and Complete → Does the Right Thing | Codebase-specific. Requires structural refactoring. Ask permission. |
| Phase 3: Combine for Design | Does the Right Thing → Intent → Domain Abstraction | Requires reading call sites and domain context. Ask permission. |
This skill operates in two modes. Pick the one that matches the user's request.
| User signal | Mode | File |
|---|---|---|
Specific identifier named ("d を改善", "DocumentManager をどうにか", "this method") | improve-mode | improve-mode.md |
| One clear target inside a code block + "リファクタリング" / "改善" | improve-mode | improve-mode.md |
| "全体の命名を見直したい", "改善余地ある?", "命名レビュー", "scan", "audit", "リストだけほしい" | audit-mode | audit-mode.md |
| Audit followup: "X だけ直して" after audit output | improve-mode (target = X) | improve-mode.md |
| Ambiguous (large code paste, no specific target, no "全体" language) | Ask the user: "全体を監査しますか、特定の識別子を改善しますか?" |
Mode = audit: Read audit-mode.md. Produce a structured table of all naming opportunities. Do not execute changes.
Mode = improve: Read improve-mode.md. Walk one identifier through phase transitions. Pause at phase boundaries.
Both modes share diagnostic criteria, transition mechanics, and red flags from reference.md.
| User signal | Stop at |
|---|---|
| "急いでる" / "bug fix" / "とりあえず" | Honest (mid Phase 1) |
| "改善して" / generic rename | Honest and Complete (end of Phase 1) |
| "リファクタリング" | Does the Right Thing (Phase 2) |
| "設計から見直したい" / "ドメイン的に整理" | Intent or Domain Abstraction (Phase 3) |
"You take the minimum steps to get the name to meet your need for the current story." — leaving names incomplete for colleagues to extend is a feature, not a flaw.
SKILL.md — this file. Router and overview.reference.md — shared 7-step diagnosis table, transitions, red flags, applesauce/probably_/AndStuff guidance.audit-mode.md — exhaustive scan workflow + output template.improve-mode.md — interactive single-target workflow + pause protocol.Read the mode file you selected, plus reference.md for diagnosis details.