refactor-safety

Identifies direct and transitive dependencies of a symbol to assess refactoring impact.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/FlexNetOS/envctl --skill refactor-safety-flexnetos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refactor-safety
Source: https://github.com/FlexNetOS/envctl/tree/main/.kb/skills/refactor-safety
Command: npx skills add https://github.com/FlexNetOS/envctl --skill refactor-safety-flexnetos

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Before making changes to code, this Skill provides a safety check by analyzing the impact of the changes on the codebase, helping to prevent breaking existing functionality.

Core Features & Use Cases

  • Impact Analysis: Determines the potential impact of refactoring on call sites, callees, and transitive dependents.
  • Code Modification Pre-check: Ensures that changes like renaming symbols, modifying types, or altering function signatures won't break the codebase.
  • Use Case: Before renaming a public method, use this Skill to see all the places where the method is called and potentially affected.

Quick Start

Run the refactor-safety skill with the symbol you want to check, e.g., refactor-safety login.

Frequently Asked Questions about refactor-safety

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

FAQPage Schema
How do I assess the impact of refactoring before modifying code?

You can perform a code modification pre-check by running the analysis with the target symbol, which identifies all call sites and transitive dependents that might be affected by altering function signatures or renaming methods.

What is a blast radius analysis when changing function signatures?

Blast radius analysis identifies the full scope of direct and transitive dependents linked to a symbol, evaluating the potential impact of altering function signatures to ensure codebase stability before changes are applied.

Can I check transitive dependencies for a public method rename without breaking the codebase?

Yes, this dependency analysis identifies all call sites and transitive dependents of the target method, evaluating the blast radius to ensure renaming or modifying types will not break existing code functionality.

Does the refactoring safety check require direct access to my codebase?

Yes, this impact assessment requires direct access to the codebase to accurately map direct and transitive symbol dependencies and evaluate the blast radius of proposed code modifications.

What are the limitations of dependency analysis for code safety?

This dependency analysis evaluates the blast radius of static symbol changes and suggests impact levels, but requires codebase access and does not dynamically execute code to verify runtime behavior.