Analyze the final diff to propose atomic commits for a clean PR history.
npx skills add https://github.com/furiosa-ai/agent_skills --skill pr-restructure
Please help me install this Agent Skill. Skill: pr-restructure Source: https://github.com/furiosa-ai/agent_skills/tree/main/pr-restructure Command: npx skills add https://github.com/furiosa-ai/agent_skills --skill pr-restructure
Clean up messy commit history into atomic commits before merge. Use when user wants to restructure PR commit history based on final diff. Triggers include:
Describe the atomic-commit plan and steps to apply it to the current branch.
High-intent search queries and answers about installing and using this skill.
Restructuring commits into atomic units involves analyzing the final diff between your base branch and HEAD to propose logical commit groupings. This cleans up messy feature branch history containing WIP changes and typo fixes by replacing it with a structured commit sequence.
An atomic commit in git history is a single, self-contained change that addresses one specific feature or fix. Restructuring your PR into atomic commits ensures each commit is logically grouped, making the diff easier to review and revert if necessary.
You can clean up a git branch with WIP commits by analyzing the final diff against the base branch and proposing a new atomic commit structure. This involves grouping related changes together and executing a safe rebase with backup steps to rewrite the history.
You can safely rewrite git commit history on a feature branch by following backup-first guidance before executing a rebase. The process identifies the base branch, analyzes the diff, and provides safe execution steps to restructure commits without losing data.
You should reorganize your PR commit history when your feature branch contains multiple small commits, WIP changes, or typo fixes. Restructuring these into atomic commits based on the final diff ensures a clean, logical history before merging into the main branch.
The best way to group git diffs into logical commits is to analyze the complete final diff between base and HEAD, then categorize changes by logical function. This atomic-commit strategy reconstructs the branch history step by step for a cleaner PR.
gihwan-devGenerate conventional commit messages for staged and unstaged Git changes.
duanegoodnerMerge worktree PRs into main and clean up associated worktrees.
stromy-orgGroup diff changes by area and create focused pull requests.
maggitPlan and execute non-interactive git rebase operations with safety checks.
