refactoring-code

Automate multi-file code refactoring with MorphLLM edit_file and dry-run previews.

35|5|Updated Jul 5, 2025
One-click install
npx skills add https://github.com/alexei-led/cc-thingz --skill refactoring-code-alexei-led
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refactoring-code
Source: https://github.com/alexei-led/cc-thingz/tree/main/plugins/dev-workflow/skills-codex/refactoring-code
Command: npx skills add https://github.com/alexei-led/cc-thingz --skill refactoring-code-alexei-led

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Batch refactoring across large codebases by applying semantic edits to multiple files with reliable merges, reducing manual toil and errors.

Core Features & Use Cases

  • Batch across files: Apply a single refactor to many files with consistency.
  • Semantic merging: Leverages code structure to minimize merge conflicts and preserve intent.
  • Dry-run previews: Preview changes before applying to ensure safety.

Quick Start

Use MorphLLM edit_file to perform a multi-file refactor across the project with a single command.

Frequently Asked Questions about refactoring-code

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

FAQPage Schema
How do I batch refactor code across multiple files?

Batch refactoring across multiple files applies a single structural update to many files simultaneously. This skill automates multi-file refactoring by applying semantic edits with MorphLLM edit_file, ensuring consistent pattern updates across large codebases.

What is semantic merging and how does it help with automated code editing?

Semantic merging leverages code structure to minimize merge conflicts and preserve intent during automated editing. It analyzes syntax and context rather than treating files as plain text, reducing errors when applying batch edits across large codebases.

Can I preview automated code edits before applying them to my codebase?

Dry-run previews allow you to review automated code edits before applying them to your codebase. You can inspect batch refactoring changes and verify safety before committing semantic merges across multiple project files.

What's the best way to do a batch rename across a large codebase?

Batch renaming across a large codebase is best handled by applying semantic edits to multiple files simultaneously. This skill uses MorphLLM edit_file to execute pattern updates and structural refactors, reducing manual toil and errors.

Does MorphLLM edit_file support structural refactors for large codebases?

MorphLLM edit_file supports structural refactors for large codebases by applying semantic edits across many files. It handles batch renames, pattern updates, and structural changes with reliable merges and dry-run previews.

When should I avoid using automated batch editing for refactoring?

Automated batch editing for refactoring should be avoided when changes require complex, context-dependent logic that semantic merging cannot safely resolve. Always use dry-run previews to verify changes before applying structural refactors to large codebases.