speckit-branch-convention-rename

Branch renaming workflow detects non-compliant Git branches, computes exact new names based on configuration, and executes changes safely using git mv after presenting a plan and requiring explicit confirmation.

Spec folder moves are executed with git mv under safety checks, updating internal references and artifacts automatically to maintain consistent Git history and prevent broken links within the .specify/ directory.

Branch rename safety checks validate the working tree, load branch-convention configuration, build a detailed rename plan, and require explicit user confirmation before applying any changes to prevent repository drift.

Yes, you can provide a specific non-compliant branch as the target. The workflow computes the required move for that individual branch and executes it after confirmation, rather than requiring all branches to be processed at once.

Yes, a .specify/ directory is required. The rename workflow applies to spec-kit projects by loading branch-convention configuration from this directory to validate and compute folder moves and branch renames safely.

Automating consistent branch and folder renames prevents repository naming drift. The workflow detects non-compliant branches and folders, computes exact new names based on configuration, and updates internal references to maintain governance.