Rename exported symbols across codebases and verify all consumer references.
npx skills add https://github.com/ZaxbyHub/opencode-swarm --skill safe-rename
Please help me install this Agent Skill. Skill: safe-rename Source: https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/generated/safe-rename Command: npx skills add https://github.com/ZaxbyHub/opencode-swarm --skill safe-rename
Manually renaming exported symbols (functions, classes, interfaces, etc.) across a codebase is extremely error-prone, often leading to missed import statements, stale usage sites, broken builds, failing tests, and silent runtime errors that take hours to debug and fix.
Use the safe-rename skill to rename the exported calculateTotal function defined in utils/payment.ts across all files that import or use it.
High-intent search queries and answers about installing and using this skill.
Safely renaming exported symbols requires updating all consumer references, including direct imports, namespace imports, and re-exports, across transitive dependent modules. This systematic workflow ensures zero stale references and prevents silent runtime errors post-rename.
The best way to rename code symbols in a large codebase is using a systematic workflow that discovers all direct importers and transitive dependents. This ensures all consumer references are updated and validated with type checks and test execution to prevent runtime errors.
Updating aliased imports and dynamic property access when renaming a class requires explicit edge-case guidance within the rename workflow. This ensures all specialized consumer references are correctly updated alongside standard direct imports to maintain code safety.
Codebase refactoring for symbol renames works with transitive dependent modules by utilizing repo mapping to identify all direct importers and downstream consumers. This ensures renaming an exported interface or constant updates every affected file across the codebase.
Renaming an exported constant causes broken builds and failing tests when manual refactoring misses stale usage sites or import statements. A systematic rename workflow eliminates these issues by enforcing mandatory type checking and test execution to verify zero breakage.
mbwsimsAnalyze direct and transitive dependents of a source file across a codebase.
AnveioEnforce lint, type safety, test coverage, and build verification in TypeScript/JavaScript projects.
coff33ninjaVerify unused imports, functions, variables, and constants before removal.
islee23520Check workspace code with language-server tooling for diagnostics and refactoring.
