메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
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.
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.
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.
Install skills from skills.sh, rename to short names, and track originals for updates.
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.
| 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. |
target: exact symbol or identifier to rename.replacement: new name.scope (optional): file, directory, package, module, or repo boundaries.For complex tasks, invoke the $design and $lint skills for naming and intent consistency standards before applying large renames.
Use programmatic rename when all are true:
Use manual rename when any are true:
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.