What problem does it solve? Renaming a public symbol or repository path is risky: text search misses identity, breaks compatibility contracts, and leaves stale references. This Skill performs identity-based renames that update every confirmed in-scope reference without touching unrelated same-named items or changing behavior. ## Core Features & Use Cases - Identity-first renaming: Resolves the declaration or tracked path before searching, distinguishing overloads, shadowing, inheritance, and generated identities from the actual target. - Compatibility governance: Requires an approved breaking-change, phased migration, alias, or adapter decision before renaming externally observable names such as API fields, config keys, or database columns. - Evidence-based verification: Re-runs identity-aware exploration after edits, classifies remaining old-name occurrences, and executes all owner-required checks (formatting, static analysis, build, tests). - Use Case: Rename a public API method across a multi-language repository, updating call sites, tests, docs, and generated code through its canonical generator, then verify with the project's build and test suite. ## Quick Start Rename the function 'getUserData' to 'fetchUserProfile' across the repository and update all its references, tests, and documentation.