gitnexus-refactoring

Map code dependencies to safely rename, extract, split, and move symbols in JavaScript or TypeScript projects.

4|1|Updated Nov 1, 2025
One-click install
npx skills add https://github.com/xtrm-dev/specialists --skill gitnexus-refactoring-xtrm-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitnexus-refactoring
Source: https://github.com/xtrm-dev/specialists/tree/main/.xtrm/skills/default/gitnexus-refactoring
Command: npx skills add https://github.com/xtrm-dev/specialists --skill gitnexus-refactoring-xtrm-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you change code structure safely when a rename, extraction, split, or move could break dependents, imports, or tests.

Core Features & Use Cases

  • Dependency-Aware Refactoring: Maps callers, callees, and references before making structural changes.
  • Safe Symbol Renames: Previews and applies multi-file symbol renames with validation.
  • Module Extraction and Splitting: Supports moving code into new modules or breaking large services into smaller parts.
  • Use Case: If you need to rename a core function across a TypeScript project, this Skill helps you update the implementation, callers, and affected tests in the right order.

Quick Start

Use the gitnexus-refactoring skill to safely rename validateUser to authenticateUser and update every dependent call site.

Frequently Asked Questions about gitnexus-refactoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely rename a function across a multi-file TypeScript project?

Safe function renaming maps code dependencies to preview symbol updates, update callers and imports, and run post-refactor tests to verify changes across multi-file TypeScript projects. This validates caller chains and prevents breaking dependent modules.

What is dependency-aware refactoring and when do I need it?

Dependency-aware refactoring maps callers, callees, and references before altering module boundaries or public APIs. You need it when extracting, splitting, or moving symbols across a codebase to prevent breaking import chains and test coverage.

How do I extract a module from a large TypeScript service without breaking imports?

Module extraction moves code into new modules by applying graph-based impact analysis to map references and caller chains. It previews structural changes and updates affected test coverage to ensure imports remain intact across the codebase.

Can I preview code changes before applying a multi-file refactor?

Yes, you can preview code changes using dry-run previews before applying multi-file refactors. This verifies the impact of renaming, splitting, or moving symbols on public APIs and caller chains before any code is modified.

Does dependency analysis refactoring work with JavaScript or only TypeScript?

Graph-based dependency analysis refactoring works with both multi-file JavaScript and TypeScript projects. It maps code dependencies to safely move symbols, update caller chains, and verify test coverage across either language environment.

What's the best way to split large modules while maintaining test coverage?

The best way to split large modules is using graph-based impact analysis to break services into smaller parts while tracking affected caller chains. It applies context lookup and post-refactor testing to verify structural changes maintain test coverage.