Run any Skill in Manus with one click

rename

Stars2

Forks1

UpdatedApril 1, 2026 at 02:35

Safely rename symbols and identifiers with scope control, ambiguity checks, and post-rename verification. Use when renaming variables, functions, types, files, or API fields across one or many files, especially when consistency and low false-positive risk matter.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

mirurobotics

mirurobotics/agent

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	rename
description	Safely rename symbols and identifiers with scope control, ambiguity checks, and post-rename verification. Use when renaming variables, functions, types, files, or API fields across one or many files, especially when consistency and low false-positive risk matter.

Rename Workflow

Inputs

target: exact symbol or identifier to rename.
replacement: new name.
scope (optional): file, directory, package, module, or repo boundaries.

References

For complex tasks, invoke the $design and $lint skills for naming and intent consistency standards before applying large renames.

Method Selection

Use programmatic rename when all are true:

At least 3 occurrences or multiple files.
Pattern is unambiguous.
Scope can be bounded safely.

Use manual rename when any are true:

Only 1-2 occurrences.
Pattern is ambiguous.
Context-dependent edits are required.

Procedure

Confirm target, replacement, and scope exactly.
Discover occurrences and classify by confidence (safe vs ambiguous).
Check for uncommitted changes and warn when rename will mix with unrelated edits.
Apply rename with the chosen method.
Verify no stale references remain.
Run relevant tests/lint checks when available and proportionate.
Report affected files and any residual risk.

Language-Specific Conventions

go: exported identifiers are PascalCase; unexported are camelCase; acronyms remain uppercase (ID, URL, HTTP).
javascript/typescript: variables/functions camelCase, classes/components PascalCase, constants SCREAMING_SNAKE_CASE.
python: functions/variables/modules snake_case, classes PascalCase, constants SCREAMING_SNAKE_CASE.
rust: functions/modules snake_case, types/traits PascalCase, constants SCREAMING_SNAKE_CASE.

Safety Rules

Avoid partial rename completion.
Avoid replacing unrelated identifiers.
Prefer symbol-aware tooling when available.
Validate casing and naming conventions for the language.

Output Contract

Rename plan (method, scope, risk notes).
Rename execution summary (files, replacement count).
Verification summary (search/tests/lint outcomes).

More from this repository

same repository

commit

mirurobotics/agent

Prepare and execute high-quality Conventional Commits from working tree changes with repository-aware commit scoping (root repo and submodules) and atomic commit planning. Use when asked to commit, split commits, draft commit messages, or organize staged/unstaged changes into safe commit units.

2026-04-012

design

mirurobotics/agent

Design and implement code changes end-to-end, from requirements clarification through implementation, validation, and documentation updates. Use when writing new code, extending features, fixing bugs, or making structured code changes where correctness, maintainability, and clear tradeoffs matter.

2026-04-012

document

mirurobotics/agent

Add or improve code and repository documentation so behavior, constraints, and usage are clear and current. Use when asked to write/update docs, docstrings, inline rationale comments, architecture notes, or change-related documentation for code updates.

2026-04-012

find-skills

mirurobotics/agent

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

2026-04-012

install-skills

mirurobotics/agent

Install skills from skills.sh, rename to short names, and track originals for updates.

2026-04-012

lint

mirurobotics/agent

Run repository linting and formatting checks, fix lint failures, and verify a clean result. Use when asked to lint code, resolve style/tooling violations, or make CI lint checks pass across changed files or whole repositories.

2026-04-012

name	rename
description	Safely rename symbols and identifiers with scope control, ambiguity checks, and post-rename verification. Use when renaming variables, functions, types, files, or API fields across one or many files, especially when consistency and low false-positive risk matter.

Rename Workflow

Inputs

target: exact symbol or identifier to rename.
replacement: new name.
scope (optional): file, directory, package, module, or repo boundaries.

References

For complex tasks, invoke the $design and $lint skills for naming and intent consistency standards before applying large renames.

Method Selection

Use programmatic rename when all are true:

At least 3 occurrences or multiple files.
Pattern is unambiguous.
Scope can be bounded safely.

Use manual rename when any are true:

Only 1-2 occurrences.
Pattern is ambiguous.
Context-dependent edits are required.

Procedure

Confirm target, replacement, and scope exactly.
Discover occurrences and classify by confidence (safe vs ambiguous).
Check for uncommitted changes and warn when rename will mix with unrelated edits.
Apply rename with the chosen method.
Verify no stale references remain.
Run relevant tests/lint checks when available and proportionate.
Report affected files and any residual risk.

Language-Specific Conventions

go: exported identifiers are PascalCase; unexported are camelCase; acronyms remain uppercase (ID, URL, HTTP).
javascript/typescript: variables/functions camelCase, classes/components PascalCase, constants SCREAMING_SNAKE_CASE.
python: functions/variables/modules snake_case, classes PascalCase, constants SCREAMING_SNAKE_CASE.
rust: functions/modules snake_case, types/traits PascalCase, constants SCREAMING_SNAKE_CASE.

Safety Rules

Avoid partial rename completion.
Avoid replacing unrelated identifiers.
Prefer symbol-aware tooling when available.
Validate casing and naming conventions for the language.

Output Contract

Rename plan (method, scope, risk notes).
Rename execution summary (files, replacement count).
Verification summary (search/tests/lint outcomes).