Skill

dev-repo-bigbang-move

Copies files from old repo to new remote, strips commit history, purges private info, commits and pushes for fresh start without history.

Git

git-workflow

npx claudepluginhub takazudo/claude-resources

Configuration

Arguments: <old-repo-path> <new-repo-path>

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Move all files from an old repo to a new repo, intentionally losing commit history. Purge private/client info from the new repo before pushing. The old repo is left untouched.

SKILL.md

Similar Skills

cache-components

139.3k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

Stats

Stars7

Forks0

Last CommitApr 5, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Big-Bang Repo Move

Move all files from an old repo to a new repo, intentionally losing commit history. Purge private/client info from the new repo before pushing. The old repo is left untouched.

Arguments

$0 — Path to the old (source) repo
$1 — Path to the new (destination) repo

If arguments are not provided, ask the user for both paths.

Workflow

Step 1: Validate Repos

Confirm $0 exists and is a git repo
Confirm $1 exists. If it is not a git repo yet, run git init and create an initial empty commit:
```
git commit --allow-empty -m "Initial commit"
```
Confirm $1 has a remote configured (git remote -v). If not, ask the user for the remote URL and add it.

Step 2: Copy Files

Copy all files from $0 to $1, excluding .git/ directory

Use rsync -av --exclude='.git' <old>/ <new>/ for reliable copy

Verify files were copied correctly

Step 3: Purge Private Info

Run /purge-private-info on the NEW repo ($1) to scan and clean private/client information.

Step 4: Commit and Push

Run /commits on the new repo to commit all files
Push to the remote: git push -u origin main (or the appropriate branch name)

Step 5: Update Old Repo Remote (Optional)

Ask the user if they want to update the old repo's remote to point to the new repo. If yes:

Get the new remote URL from $1: git -C $1 remote get-url origin
Update the old repo's remote: git -C $0 remote set-url origin <new-url>

Step 6: Summary

Report what was done:

Files copied from old to new repo
Private info purged (summary from purge step)
New repo committed and pushed
Whether old repo remote was updated

Important Notes

Never modify the old repo's files or history — only optionally update its remote URL
All commit history is intentionally lost — this is a fresh start
The old repo remains as-is for reference
Always confirm with the user before pushing