One-click install
npx skills add https://github.com/mirkobozzetto/flowflow --skill gitnexus-refactoring-mirkobozzetto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitnexus-refactoring
Source: https://github.com/mirkobozzetto/flowflow/tree/main/.agents/skills/gitnexus/gitnexus-refactoring
Command: npx skills add https://github.com/mirkobozzetto/flowflow --skill gitnexus-refactoring-mirkobozzetto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Refactoring code often breaks behavior because renames, moves, and extractions ripple through call sites and dependencies that are hard to find reliably.

Core Features & Use Cases

  • Safe renames: Rename symbols across multiple files while distinguishing high-confidence graph edits from lower-confidence AST search edits.
  • Structural changes: Extract modules, split functions/services, and move code while updating imports and callers in the correct order.
  • Change verification: Detect and validate the exact set of files, symbols, and affected processes changed, and then run the relevant tests.
  • Dependency & flow mapping: Use impact mapping, flow queries, and incoming/outgoing reference context to understand what must be updated first.

Quick Start

Tell your AI to refactor the targeted symbol by mapping dependents, updating in a safe order (interfaces → implementations → callers → tests), then verifying the resulting change scope and running the affected tests.

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

Safe symbol renaming across multiple files requires mapping dependents and execution flows to distinguish high-confidence graph edits from lower-confidence AST search edits, ensuring all callers and imports are updated correctly.

What is the best way to extract modules and split functions while updating imports?

Extracting modules and splitting functions safely involves mapping incoming and outgoing references, then updating imports and callers in a deterministic order: interfaces first, then implementations, callers, and finally tests.

How does dependency impact analysis work before applying structural code changes?

Dependency impact analysis uses flow queries and reference context mapping to identify affected files, symbols, and processes, ensuring deterministic planning and risk-aware review of edits before structural code changes are applied.

Can I verify that my refactoring changes did not break existing behavior?

Change verification after refactoring detects the exact set of modified files, symbols, and affected processes, then runs the relevant tests to validate that no existing behavior is broken.

What's the safest order to update code when moving functions across modules?

The safest order to update code during structural refactoring is interfaces, implementations, callers, and then tests, ensuring dependency awareness and minimizing the risk of breaking execution flows.

Why do AST search edits break behavior during git refactoring?

AST search edits can break behavior during git refactoring because they lack dependency awareness, failing to map execution flows and distinguish high-confidence graph edits from lower-confidence references across multiple files.