Naming analyzer: better variable, function and class names
Audit identifiers against language conventions, flag vague/misleading/abbreviated names, and propose better ones with reasoning — plus a full report format and a decision tree
- What
- Audit identifiers against language conventions, flag vague/misleading/abbreviated names, and propose better ones with reasoning — plus a full report format and a decision tree
- Cost
- Free
- Needs
- a codebase to analyze — the skill is guidance the agent follows, not software to install
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @softaworks's naming-analyzer skill: a naming-convention expert for your agent. It analyzes existing names (variables, constants, functions, methods, classes, interfaces, types, files, directories, database tables and columns, API endpoints), identifies issues (unclear or vague names, misleading names that don't match behavior, obscuring abbreviations, inconsistent conventions, too-short/too-long names, Hungarian notation misuse, single-letter variables outside loops), checks conventions per language (JS/TS camelCase/PascalCase/UPPER_SNAKE_CASE, Python snake_case, Java camelCase, Go PascalCase-exported with all-caps acronyms like HTTPServer), and provides suggestions with reasoning. It ships a full naming-analysis report format (summary counts, critical/major/minor issues with file:line, current vs suggestion vs reason, convention violations), naming patterns to follow, DO/DON'T best practices, a boolean/function/class/constant decision tree, and offers to create a refactoring script to apply the changes. Honest caveats: pure advisory guidance — it suggests names, it doesn't run the refactors itself (the refactoring script is offered, not automatic); examples skew JavaScript but the convention tables cover Python, Java and Go too. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a codebase to analyze — the skill is guidance the agent follows, not software to install Install "Naming analyzer: better variable, function and class names" for me. It gives my agent @softaworks's naming-analyzer skill: analyze existing identifiers, identify naming issues (vague, misleading, abbreviated, inconsistent), check per-language conventions (JS/TS, Python, Java, Go), suggest better names with reasoning, produce a structured naming-analysis report, and offer a refactoring script. MIT-licensed. Repository: https://github.com/softaworks/agent-toolkit/blob/main/dist/plugins/naming-analyzer/skills/naming-analyzer/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "naming-analyzer". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at the files to analyze; nothing else — it's advisory). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.