gitnexus-refactoring

Refactor code across a codebase with GitNexus for renaming, extracting, and moving components.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/MDLDev-site/mdl-brand-website --skill gitnexus-refactoring-mdldev-site
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitnexus-refactoring
Source: https://github.com/MDLDev-site/mdl-brand-website/tree/main/.claude/skills/gitnexus/gitnexus-refactoring
Command: npx skills add https://github.com/MDLDev-site/mdl-brand-website --skill gitnexus-refactoring-mdldev-site

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Refactoring code can introduce bugs, break dependencies, and drift tests. This Skill provides a safe, auditable workflow for renaming symbols, extracting modules, splitting services, and moving code across a codebase using GitNexus, with built-in checks and dependency awareness.

Core Features & Use Cases

  • Safe symbol renaming with dependency updates across callers and imports.
  • Module extraction and service splitting with updated interfaces and imports.
  • Context and impact analysis to map execution flows, ensuring changes are scoped correctly.
  • Change verification and test guidance to validate edits before applying them.

Quick Start

Plan a refactor by running gitnexus_rename with symbol_name and new_name in dry_run to preview edits.

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 symbol and update all dependencies across a codebase?▼

To safely rename a symbol across a codebase, run a dry run to preview edits, perform context queries for impact analysis, and update all callers and imports. This validates changes before applying them.

What is the best way to extract modules or split services without breaking imports?▼

The best way to extract modules or split services without breaking imports is using a workflow with dependency tracing and impact analysis. This maps execution flows and automatically updates interfaces across files and packages.

How does impact analysis map execution flows during code restructuring?▼

Impact analysis maps execution flows during code restructuring by performing context queries that trace dependencies. This ensures changes are scoped correctly and validates edits before they are applied to the codebase.

Can I preview code refactoring edits before applying them to the repository?▼

Yes, you can preview code refactoring edits before applying them by running a dry run. This allows you to validate changes, check for dependency breaks, and verify test guidance before committing to the repository.

Does this refactoring workflow support moving code across different files and packages?▼

Yes, this refactoring workflow supports moving code across files and packages. It includes change detection and dependency awareness to ensure that all interfaces and imports are correctly updated during the move.

When should I not use automated code restructuring for renaming symbols?▼

You should not use automated code restructuring for renaming symbols without first running a dry run to preview edits. Skipping impact analysis and change verification can introduce bugs and break dependencies across callers.