Clean copy
SkillDev toolsThe clean-copy skill rebuilds a messy git branch as a new branch with a clean, narrative-quality commit history. It studies the changes between the current branch and main, then recreates that work on a fresh branch as a series of logical, well-described commits. It verifies the final state matches the original and can open a pull request linking back to the source branch.
Then ask your AI: use the Clean copy skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.
No other account needed.
Have a git repository with a main branch and a source branch that has no uncommitted changes or merge conflicts.
What your AI can do with it
- Study the diff between the current branch and main
- Create a new branch from main with a chosen name
- Reimplement changes as logical, well-described commits
- Verify the clean branch matches the source branch
- Open a pull request linking back to the source branch
Getting started
- Have a git repository with a main branch and a source branch that has no uncommitted changes or merge conflicts.
- Ensure the source branch is up to date with main.
- Ask the agent to make a clean copy branch, optionally providing a name for the new branch.
- Let the agent analyze the diff and recreate the work as a series of commits.
- Review the new branch and the pull request it opens.
What this skill tells your AI
The instructions your AI receives, as published by tldraw/tldraw in skills/clean-copy/SKILL.md and read by Ahel’s review.
Reimplement the current branch on a new branch with a clean, narrative-quality commit history suitable for reviewer comprehension.
Workflow
- Gather context:
- Source branch:
git branch --show-current. - Working tree:
git status --short. - Commits since main:
git log main..HEAD --oneline. - Diff summary:
git diff main...HEAD --stat.
- Source branch:
- Validate the source branch:
- Ensure there are no uncommitted changes or merge conflicts.
- Confirm the source branch is up to date with
main.
- Choose the new branch name:
- Use the user's requested name when provided.
- Otherwise use
<source-branch>-clean.
- Analyze the diff:
- Study all changes between the source branch and
main. - Understand the final intended state before recreating it.
- Study all changes between the source branch and
- Create the clean branch from
main. - Plan the commit storyline:
- Break the implementation into self-contained logical steps.
- Each step should read like a stage of development in a tutorial.
- Reimplement the work:
- Recreate the final changes step by step.
- Commit after each coherent idea.
- Use clear commit subjects and descriptions.
- Use
git commit --no-verifyfor intermediate commits so hooks do not block temporarily incomplete states.
- Verify correctness:
- Confirm the final clean branch state exactly matches the original source branch.
- Run the final commit without
--no-verifyso normal checks run.
- Open a pull request using the
prskill.- Include a link to the original branch in the PR description.
Rules
- Never add yourself or an AI tool as an author, contributor, or co-author.
- Never include AI attribution in commits or PR content.
- The final clean branch must be identical to the source branch.
- Do not force push unless the user explicitly asks for it.
Signals
- GitHub stars
- 51k
- Forks
- 4k
- Last commit
- Oct 2026
Questions
- What does the skill do?
- It reimplements the current branch on a new branch with a clean, narrative-quality git commit history suitable for reviewer comprehension.
- When should I use it?
- Use it when asked to make a clean copy branch, clean up commit history by replaying work, or rebuild a branch as reviewable commits.
- Does it add AI attribution to commits?
- No. The skill never adds an AI tool as an author, contributor, or co-author, and never includes AI attribution in commits or PR content.
- Will the final branch be identical to the source branch?
- Yes. The skill verifies that the final clean branch state exactly matches the original source branch.
Advanced
- Item type
- skill
- Key
clean-copy-tldraw- Source
- github.com/tldraw/tldraw