Run any Skill in Manus with one click

$pwd:

clean-copy

Name: Clean Copy
Author: 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 history by replaying work, or rebuild a branch as reviewable commits.

Run Skill in Manus

$ git log --oneline --stat

stars:47,209

forks:3,233

updated:April 27, 2026 at 14:22

SKILL.md

readonly

name	clean-copy
description	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 history by replaying work, or rebuild a branch as reviewable commits.

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.

related-skills.json

same repository

tldraw-migrate.md

from "tldraw/tldraw"

Migrate a project to a newer version of the tldraw SDK. Use when upgrading tldraw packages, fixing TypeScript errors after a tldraw upgrade, or when the user mentions tldraw migration.

2026-05-2147.2k

write-pr.md

from "tldraw/tldraw"

Reference standards for writing pull request titles and descriptions in the tldraw repository. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.

2026-05-2147.2k

write-release-notes.md

from "tldraw/tldraw"

Writing release notes articles for tldraw SDK releases. Use when creating new release documentation, drafting release notes from scratch, or reviewing release note quality. Provides guidance on structure, voice, and content for release files in `apps/docs/content/releases/`.

2026-05-0647.2k

pr-walkthrough.md

from "tldraw/tldraw"

Create a narrated video walkthrough of a pull request with code slides and audio narration. Use when asked to create a PR walkthrough, PR video, or walkthrough video.

2026-04-2847.2k

commit-changes.md

from "tldraw/tldraw"

Create a git commit for the current changes. Use when asked to commit changes, make a commit, generate a commit message, or commit the current worktree with optional user-provided context.

2026-04-2747.2k

issue.md

from "tldraw/tldraw"

Create and research a GitHub issue in the tldraw repository from a user description. Use when the user invokes issue, asks to create an issue, report a bug, file a feature request, or add research to a new issue.

2026-04-2747.2k

package.json

"author": "tldraw"

"repository": "tldraw/tldraw"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

name	clean-copy
description	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 history by replaying work, or rebuild a branch as reviewable commits.

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.

clean-copy

Clean copy

Workflow

Rules

More from this repository

More from this repository

Clean copy

Workflow

Rules