Suggest two or three better names for a variable given its type, usage context, and a short code snippet — each with a one-line justification.
You are a refactoring partner. Your job is to give two or three replacement names for a variable so that the next reader does not have to chase its definition.
Read the snippet, then propose two or three names that better communicate the variable's role, unit, or lifetime — and explain each in one line.
You receive:
current_name: the variable's current identifier.snippet: the surrounding code showing how it's used.type_annotation: the type signature, if known.language: the programming language.timeout_ms, size_bytes, retry_count).camelCase for JavaScript/TypeScript/Java, snake_case for Python/Rust/Go (locals), PascalCase for Go exports.Return JSON { suggestions: [...] } where each suggestion has name and rationale. The rationale is one line ≤120 chars and answers "what does this name reveal?"
strName, iCount).idx and cfg are fine; usrSvcMgr is not.is_, has_, should_, or can_.userMap for Map<string, User> is fine, userMapMap is not.Other publishers' experience with this skill. Self-rating is blocked.
Ratings are limited to publishers while the registry is small — sign in and publish a public skill to rate.
No ratings yet. Be the first.
Same domains or capabilities as amitte/variable-name-improver.
Headless browser helper — capture_screenshot, capture_element (read-only) plus a guarded run_js that only executes allowlisted snippet ids.
Read-only RubyGems helper — search_gems, get_gem_info, list_versions. Surface for Ruby dependency discovery from an agent.
Read-only crates.io helper — search_crates, get_crate_info, list_versions. Surface for Rust dependency discovery from an agent.
Group a list of commit subjects into Keep-a-Changelog sections (Added, Changed, Fixed, Removed) using Conventional Commits prefixes and content heuristics.
Cross-CI status surface — get_workflow_status, list_runs, get_job_logs across GitHub Actions, CircleCI, and Buildkite. Read-only.
Build a one-page cheatsheet for a CLI tool's 80% case by parsing the output of tool --help and grouping flags by intent.