clean-copy

Reformat a feature branch into a clean, atomic commit history on a new branch.

2|2|Updated Dec 30, 2025

Search Tags:#git #branching #review #pull-request #commit-history #code-cleanup

Ready to run

npx skills add https://github.com/NavarrePratt/claude-settings --skill clean-copy-navarrepratt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clean-copy
Source: https://github.com/NavarrePratt/claude-settings/tree/main/skills/clean-copy
Command: npx skills add https://github.com/NavarrePratt/claude-settings --skill clean-copy-navarrepratt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reformat messy, multi-branch histories into a single, coherent, narrative commit history on a new clean branch, making it easier for reviewers to understand the changes.

Core Features & Use Cases

Rebuilds the commit history on a new branch from main to present a clear, logical progression of changes.
Ensures atomic commits, each capturing a single idea, with descriptive messages suitable for PR review.
Provides a structured plan before execution and verifies the final state matches the original branch.

Quick Start

Reimplement the current branch on a new branch named '{branch}-clean' from main with a clean, narrative commit history.

Frequently Asked Questions about clean-copy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I clean up a messy git commit history before a pull request?▼

Yes, you can reformat a noisy multi-branch history into a single narrative commit history. The process rebuilds your commits on a new clean branch from main to present a logical progression of changes.

How do I squash small commits into atomic commits for a code review?▼

To squash commits for code review, rebuild the branch history by grouping changes into atomic commits that each capture a single idea. This ensures descriptive messages suitable for PR review.

Does cleaning a git branch history require an explicit commit plan?▼

Yes, cleaning a git branch history requires an explicit commit plan. The process provides a structured plan before execution and verifies that the final clean branch exactly matches the original work when diffed.

What is the best way to prepare a feature branch with many merges for review?▼

The best way to prepare a feature branch with many merges is to reformat it across branches into a clean, narrative git history on a new branch. This makes the evolution of changes easier for reviewers to understand.

Does rewriting commit history change the original branch?▼

Rewriting commit history does not change the original branch. It rebuilds the commit history on a new branch named with a '-clean' suffix from main, ensuring the original work remains untouched.