gitnexus-refactoring

Map dependencies and execution flows to safely rename, extract, split, or move code.

2|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/tu11aa/squadrant --skill gitnexus-refactoring-tu11aa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitnexus-refactoring
Source: https://github.com/tu11aa/squadrant/tree/main/.claude/skills/gitnexus/gitnexus-refactoring
Command: npx skills add https://github.com/tu11aa/squadrant --skill gitnexus-refactoring-tu11aa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gitnexus, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of safely refactoring code, such as renaming, extracting, splitting, or restructuring code, by providing a structured workflow and tools to minimize risk and impact.

Core Features & Use Cases

  • Code Refactoring: Offers a workflow for renaming symbols, extracting modules, splitting functions/services, and more.
  • Impact Analysis: Maps all dependents and execution flows to inform refactoring decisions.
  • Risk Management: Provides tools to detect changes and verify the scope of refactorings, with risk rules to guide the process.

Quick Start

Use the gitnexus_rename command to rename a function, for example: gitnexus_rename({symbol_name: "oldName", new_name: "newName", dry_run: true}).

Frequently Asked Questions about gitnexus-refactoring

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

FAQPage Schema
How do I safely refactor code with complex dependencies?

Mapping dependencies and execution flows before modifying code allows you to verify the scope of refactorings and detect changes, minimizing the risk of breaking complex codebases.

How do I rename a function across a large codebase?

You can rename a function across a large codebase by executing an automated rename command with the old symbol name and new name, optionally running a dry run first to preview the impact.

Can I preview the impact of splitting a service before applying changes?

Yes, you can preview the impact of splitting a service by running the operation in dry run mode, which maps dependents and execution flows to show the refactoring scope without modifying files.

Do I need to install gitnexus before using this refactoring workflow?

Yes, installing gitnexus is required, as the refactoring workflow depends on it to map execution flows, detect changes, and manage risk rules within complex codebases.

What is the best way to extract a module without breaking execution flows?

The best way to extract a module without breaking execution flows is to map all dependencies first, apply risk rules to guide the process, and verify the refactoring scope before execution.