Rebase a feature branch into logical commits for PR review.
npx skills add https://github.com/apocohq/skills --skill cleanup-commits
Please help me install this Agent Skill. Skill: cleanup-commits Source: https://github.com/apocohq/skills/tree/main/skills/cleanup-commits Command: npx skills add https://github.com/apocohq/skills --skill cleanup-commits
Rebase and reorganize commits into clean, meaningful commits for easy PR review.
Run the cleanup-commits process to rebase and rewrite your current branch into clean, review-friendly commits.
High-intent search queries and answers about installing and using this skill.
To reorganize git commits before a PR review, you rebase your current feature branch to group changes into clean, logical categories like features, refactors, and tests. This requires a clean working tree in an existing git repository.
The best way to break a complex feature branch into logical commits is using git rebase to rewrite history. This separates mixed changes into distinct review-friendly commits for features, refactors, tests, and documentation.
Yes, you need a clean working tree to rebase and rewrite commit history. A clean state ensures the rebase process can safely reorganize commits without conflicts or losing uncommitted changes.
Yes, you can optionally specify a base branch to rebase onto when cleaning up commits for a PR. This allows you to integrate upstream changes while reorganizing your feature branch into review-friendly commits.
You should clean up your git history before pushing to avoid broken PRs and make code review easier. Validating repository state and verifying rebase results ensures your branch contains meaningful, logical commits.
TMI-appsValidate and push committed Git changes to a remote repository.
andeartCreate a feature-branch pull request by cherry-picking unpushed commits.
julianromliVerify tests pass, determine the base branch, and present four completion options.
maggitPlan and execute non-interactive git rebase operations with safety checks.
