Run any Skill in Manus with one click

rename-symbol-literally

Stars5

Forks0

UpdatedJune 28, 2026 at 12:02

Editor primitive for exact token replacement, not semantic refactoring. Use inside write-code-by-hand mode when the user asks to rename an exact symbol, token, string, or identifier and provides both old and new text.

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

valsteen

valsteen/write-code-by-hand

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-symbol-literally
description	Editor primitive for exact token replacement, not semantic refactoring. Use inside write-code-by-hand mode when the user asks to rename an exact symbol, token, string, or identifier and provides both old and new text.

Rename Symbol Literally

Replace an exact token with another exact token. This is text editing, not semantic refactoring.

Operational framing: deliver semantic-risk-free renaming by avoiding semantics.

Required Inputs

Search scope: current file, listed files, or repository.
Exact old token.
Exact new token.
Confirmation after showing match count.

Rules

Match exact text only.
Do not rename based on meaning.
Do not alter case variants unless explicitly requested.
Show match locations before applying repository-wide changes.
If the token appears in strings, comments, generated files, or vendored code, ask whether those matches are included.

Output

Before changing:

Found <n> exact match(es) for <old-token>.

After changing:

Replaced <n> exact occurrence(s) of <old-token> with <new-token>.

More from this repository

same repository

delete-range

valsteen/write-code-by-hand

Editor primitive for deleting an exact line range after explicit confirmation. Use inside write-code-by-hand mode when the user asks to delete, remove, or cut specific lines or a selected range.

2026-06-285

goto

valsteen/write-code-by-hand

Editor primitive for selecting the current file, line, range, function, or end-of-file cursor position. Use inside write-code-by-hand mode when the user asks to go to, select, focus, open at, jump to, or move the cursor.

2026-06-285

insert-block

valsteen/write-code-by-hand

Editor primitive for inserting an exact user-provided text block at a specified location or current cursor. Use inside write-code-by-hand mode when the user asks to insert, add, paste, append, or put this exact block somewhere.

2026-06-285

look

valsteen/write-code-by-hand

Editor primitive for listing directories and showing exact file contents or line ranges without interpreting or changing code. Use inside write-code-by-hand mode when the user asks to look, open, show, list, inspect, or display files.

2026-06-285

move-file

valsteen/write-code-by-hand

Editor primitive for moving or renaming files when the user provides exact source and destination paths. Use inside write-code-by-hand mode when the user asks to move, rename, copy, or relocate a file.

2026-06-285

replace-line

valsteen/write-code-by-hand

Editor primitive for replacing one specific line with exact user-provided text. Use inside write-code-by-hand mode when the user asks to replace a line, change this line to, or set line N to exact text.

2026-06-285

name	rename-symbol-literally
description	Editor primitive for exact token replacement, not semantic refactoring. Use inside write-code-by-hand mode when the user asks to rename an exact symbol, token, string, or identifier and provides both old and new text.

Rename Symbol Literally

Replace an exact token with another exact token. This is text editing, not semantic refactoring.

Operational framing: deliver semantic-risk-free renaming by avoiding semantics.

Required Inputs

Search scope: current file, listed files, or repository.
Exact old token.
Exact new token.
Confirmation after showing match count.

Rules

Match exact text only.
Do not rename based on meaning.
Do not alter case variants unless explicitly requested.
Show match locations before applying repository-wide changes.
If the token appears in strings, comments, generated files, or vendored code, ask whether those matches are included.

Output

Before changing:

Found <n> exact match(es) for <old-token>.

After changing:

Replaced <n> exact occurrence(s) of <old-token> with <new-token>.