smithery/sounder25

Project-Wide Rename

Safely renames a .NET project (solution, projects, namespaces, directories) from one name to another. Supports Planned (clean) and Recovery (dirty) modes.

Installation

$ npx skills add smithery/sounder25 --skill project-wide-rename

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/sounder25 · top by installs.

npx skills add smithery/sounder25

Browse all from smithery/sounder25

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0
Declared agents antigravity

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,027 B
  • docs SUMMARY.md 181 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

SKILL-002: Project-Wide Rename

Overview

Renaming a complex .NET solution is error-prone. This skill automates the process of renaming files, directories, text content, and git configuration, with safety mechanisms to prevent data loss.

Trigger Phrases

  • rename project <old> <new>
  • safe rename <old> to <new>
  • fix pending rename

Inputs

Parameter Type Required Default Description
--old-name string Yes - Original project name (e.g., "Scrutor")
--new-name string Yes - New project name (e.g., "ELR")
--mode string No auto planned, recovery, or auto
--dry-run switch No False Preview changes (mandatory if dirty)

Modes

  1. Planned Mode: Requires a clean git status. Best for starting a rename operation from scratch.
  2. Recovery Mode: Allows dirty git status. Best for finishing a partial rename or cleaning up a manual attempt.

Outputs

  1. Console Output: Progress log of renamed files and updated content.
  2. Report: RENAME_SUMMARY.md with list of changes.
  3. Git Branch: rename-<old>-to-<new> containing the changes.

Preconditions

  1. Git repository root.
  2. .NET SDK installed (for build verification).
  3. Permissions to modify all files.

Safety/QA Checks

  1. Exclusions: Ignores bin, obj, .git, node_modules.
  2. Build Check: optional verification build after rename.
  3. Rollback: Ability to git reset --hard if something goes wrong.

Implementation

See rename_project.ps1.

Integration

# Example
.\skills\02_project_rename\rename_project.ps1 -OldName "Scrutor" -NewName "ELR" -DryRun