Menu

Individual skill

naming-consultant

0upvotes

Suggests consistent, well-reasoned names for variables, functions, files, or classes given context. Use when a name feels off, ambiguous, or inconsistent with surrounding conventions.

skills/utilities/naming-consultant/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
27
Repository last updated
Aug 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Purpose

Suggest clear, consistent names for code elements (variables, functions, classes, files) based on what they actually do and the naming conventions already in use nearby — not generic naming advice detached from context.

## When to Use

- A name feels vague, misleading, or inconsistent with the rest of the codebase.
- Naming something new and want options grounded in existing conventions.
- Reviewing a PR and a name doesn't clearly communicate intent.

## What to Analyze / Do

1. **Understand what the thing actually does** — a name should reflect behavior/purpose, not implementation detail that might change.
2. **Check surrounding naming conventions** — casing style (camelCase/snake_case/PascalCase), verb conventions (`get`/`fetch`/`load` for retrieval — pick whichever the codebase already uses consistently), boolean naming (`is`/`has`/`should` prefixes), and match them rather than introducing a new convention.