Rename and Reorganise a Repository Structure
Tidy folders and names with minimal disruption.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Propose a cleaner structure. Current layout: [CURRENT_LAYOUT]. Language and tools: [STACK]. Team size: [TEAM_SIZE]. Pain points: [PAIN_POINTS]. Suggest a target layout with the reason for each folder, naming conventions, and where tests, docs, scripts and configuration live. Plan the move in steps that keep history readable, update imports and build paths, and avoid long-lived branches. Coordinate with the team to freeze changes briefly. Return the old to new mapping as a table, a script outline to perform and verify the move, a checklist for continuous integration and deployment paths, and a communication message. Stop and ask if any location has special meaning for the tools I use. Provide a script outline using version control commands that move files while preserving history, and the checks to run afterwards: build, tests, links in documentation, and paths in continuous integration configuration. Add a rollback approach if something breaks after merge, and a short guide for teammates on updating their branches after the move.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.