02_project_rename_skill

Overview

This skill safely renames a .NET solution and its projects by updating filenames, directories, project files, namespaces, and git metadata. It offers Planned (clean) and Recovery (dirty) modes and generates a change report and a dedicated git branch for review. The tool includes dry-run previews, build verification, and rollback options to prevent data loss.

How this skill works

The script scans the repository excluding build and VCS artifacts, finds occurrences of the old name in filenames, directory names, project/solution files, and source code, and applies deterministic replacements. It creates a branch named rename-<old>-to-<new>, logs each change to the console, writes RENAME_SUMMARY.md, and optionally runs a .NET build to verify integrity. Planned mode enforces a clean git state; Recovery mode permits changes on a dirty working tree but requires a dry-run for safety.

When to use it

• You need to rename a solution, project, or root namespace across a repository.
• You want a repeatable, auditable rename with a branch and summary report.
• A prior manual rename left the repo in a partial or inconsistent state (use Recovery mode).
• You want to inspect changes first with a dry run before committing.
• You must maintain build verification after renaming to catch breakages.

Best practices

• Run the script from the git repository root and ensure .NET SDK is installed.
• Start with a dry run to review all planned edits before committing.
• Use Planned mode on a clean git working tree for the safest operation.
• If work is in progress, use Recovery mode with the dry-run flag to avoid data loss.
• Review RENAME_SUMMARY.md and test a full build on the rename branch before merging.

Example use cases

• Rename an entire solution from Scrutor to ELR and update all namespaces and project files.
• Finish and clean up a partially applied manual rename that left inconsistent references.
• Create a rename branch for a planned rebranding and produce an audit-friendly summary for reviewers.
• Perform a dry-run to preview every filename and text replacement before approving changes.