gitnexus-refactoring

Rename symbols and extract modules while preserving dependencies across a repository.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/gerald-ica/opencode-config-snapshot --skill gitnexus-refactoring-gerald-ica
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitnexus-refactoring
Source: https://github.com/gerald-ica/opencode-config-snapshot/tree/main/opencode/skills/gitnexus-refactoring
Command: npx skills add https://github.com/gerald-ica/opencode-config-snapshot --skill gitnexus-refactoring-gerald-ica

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This module helps developers safely rename symbols, extract modules, split services, and move code within a codebase, reducing risk and keeping dependencies intact during refactors.

Core Features & Use Cases

  • Safe symbol renaming across files with dependency awareness
  • Module extraction and service splitting with minimal disruption
  • Guidance for planning refactors, verifying changes, and updating tests

Quick Start

Execute gitnexus_rename to safely rename a symbol across the repository and propagate changes.

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 across multiple files without breaking dependencies?

To safely rename a symbol across files, execute gitnexus_rename to propagate changes throughout the repository while preserving dependency integrity. It applies safe renaming mechanisms to reduce manual errors during code refactoring.

What is the best way to extract a module or split a service with minimal disruption?

The best way to extract a module or split a service is using guided refactoring commands that restructure code while keeping dependencies intact. This approach minimizes disruption and reduces risk during service splitting.

How do I assess the impact of moving code within a repository before applying changes?

Assess the impact of moving code by running gitnexus_impact to verify dependencies and analyze potential disruption. This verifies changes before execution, ensuring safe code movement across the repository.

Can I use this refactoring approach to restructure code in any repository?

Yes, you can use this refactoring approach to restructure code in any repository by applying safe renaming, module extraction, and code movement. It relies on dedicated commands to preserve dependencies during structural changes.

What should I do to verify changes and update tests after a code refactor?

To verify changes and update tests after a code refactor, follow the provided guidance for planning refactors and validating modifications. This ensures dependencies remain intact and the codebase stays stable post-restructuring.