skills.rest
yungweng
yungwengCOMMUNITY
Explore all skills by this author →
Website𝕏@yannickwengerGitHub

gitnexus-refactoring

Analyze code dependencies and automate multi-file symbol updates for safe refactoring.

3|Updated Dec 30, 2025
Search Tags:#developer tools#code analysis#refactoring#dependencies#code safety#gitnexus
One-click install
npx skills add https://github.com/yungweng/dotfiles --skill gitnexus-refactoring-yungweng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitnexus-refactoring
Source: https://github.com/yungweng/dotfiles/tree/main/claude/.claude/skills/gitnexus-refactoring
Command: npx skills add https://github.com/yungweng/dotfiles --skill gitnexus-refactoring-yungweng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers safely refactor code by understanding the blast radius of changes and mapping dependencies, reducing the risk of introducing bugs.

Core Features & Use Cases

  • Dependency Mapping: Visualize upstream and downstream dependencies of code elements.
  • Automated Renaming: Safely rename functions, variables, and other symbols across multiple files.
  • Code Restructuring: Assist in extracting code into new modules or splitting functions/services.
  • Use Case: When asked to "Rename this function safely," the skill will first map all its dependents, then perform a dry run of the rename operation, allowing for review before applying changes.

Quick Start

Use the gitnexus refactoring skill to safely rename the function 'validateUser' to 'authenticateUser' by running the command gitnexus_rename({symbol_name: "validateUser", new_name: "authenticateUser", 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 across multiple files without breaking dependencies?▼

Safe code refactoring across multiple files requires mapping the blast radius of changes and analyzing upstream and downstream dependencies. This skill automates multi-file symbol updates by performing impact analysis before applying modifications.

How does dependency mapping work for automated code renaming?▼

Dependency mapping for code renaming works by visualizing all upstream and downstream dependents of a symbol. The skill runs a dry run of the rename operation first, allowing you to review the exact impact before committing changes.

Can I extract code into new modules or split functions safely?▼

Yes, you can extract code into new modules or split functions safely. The skill facilitates code restructuring by mapping dependencies and automating multi-file symbol updates to reduce the risk of introducing bugs.

What is the best way to analyze the impact of renaming a function?▼

The best way to analyze the impact of renaming a function is to run a dry rename operation. The skill uses impact analysis tools to map all dependents of the symbol, allowing you to review the blast radius before applying changes.

Do I need to run a dry run before applying code refactoring changes?▼

Yes, running a dry run is recommended before applying code refactoring changes. The skill performs a dry run of operations like renaming to map dependents and display the exact impact, allowing for safe review prior to modification.

Related Skills

Explore More Software Engineering Skills→
s1366560s1366560
5

gitnexus-refactoring

Automate code refactoring with GitNexus dependency mapping and impact analysis.

Community
Advanced
drhaltodrhalto
51

mako-graph

Trace dependency paths and estimate change impact across project files.

Community
Advanced
lucasfdigitallucasfdigital

gitnexus-refactoring

Automate code refactoring with impact analysis and verification across a codebase.

Community
Advanced
ptarmiganlabsptarmiganlabs
58

gitnexus-refactoring

Automate code refactoring with GitNexus dependency analysis and step-by-step workflows.

Official
Advanced