Labsco
tldraw logo

clean-copy

★ 48,500

by tldraw · part of tldraw/tldraw

Reimplement the current branch on a new branch with a clean, narrative-quality git commit history. Use when asked to make a clean copy branch, clean up commit…

🔥🔥🔥✓ VerifiedFreeQuick setup
#automation#git
🧰 Not standalone. This skill ships with tldraw/tldraw and only works together with that tool — install the tool first, then add this skill.

Reimplement the current branch on a new branch with a clean, narrative-quality git commit history. Use when asked to make a clean copy branch, clean up commit…

Inspect the full instructions your agent will receiveExpand

This is the exact playbook injected into your agent when the skill activates — shown here so you can audit it before installing. You don't need to read it to use the skill.

by tldraw

Reimplement the current branch on a new branch with a clean, narrative-quality git commit history. Use when asked to make a clean copy branch, clean up commit… npx skills add https://github.com/tldraw/tldraw --skill clean-copy Download ZIPGitHub48.5k

Clean copy

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.

  • 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.

  • 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-verify for 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-verify so normal checks run.

  • Open a pull request using the pr skill.

  • 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.