Commit History Cleanup Review Before You Open a Pull Request
Review a messy Git commit list, spot vague messages and mixed changes, and get a clean grouping plan with rewritten messages and a scoring table.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Review the commit history on my branch before I open a pull request. Branch name: [BRANCH_NAME]. The output of my commit list (hash, message, files changed): [COMMIT_LIST]. The purpose of the branch: [BRANCH_PURPOSE]. My team's rules on squashing and history: [HISTORY_RULES]. Score every commit from 1 to 5 on three things: message clarity, single purpose, and safe to revert on its own. Present a table with columns Commit, Message clarity, Single purpose, Revertable, Total (out of 15), Comment. Then give: 1. A count of commits scoring under 9 and what they have in common. 2. A proposed regrouping into 2 to 6 logical commits, with a new message for each (subject under 50 characters, body if needed). 3. For each regroup, which old commits would be combined, explained in words. 4. The git approach options (interactive rebase, squash on merge, leaving it alone) with pros and cons, and a recommendation based on my team's rules. Do not give me commands that rewrite shared history; if the branch has been pushed, warn me about force-push risks and suggest asking the team. 5. Anything in the list that looks like it may contain secrets, debug code or generated files, based only on the file names and messages I pasted. I will run any commands myself; do not tell me to run destructive commands without a backup branch step first. Do not invent commits.
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.