ac-git-git-safe

Git Safe

Safely rewrite git history with mandatory dry-run planning and user confirmation.

Critical Rules

1. ALWAYS DRY RUN FIRST - Propose plan, never execute without approval
2. ALWAYS WAIT FOR CONFIRMATION - User must explicitly approve before destructive operations
3. ALWAYS CREATE BACKUP - Backup branch before any rebase/amend
4. ALWAYS SAVE TAG MESSAGES - Preserve tag annotations before deletion

Supported Operations

Operation	Use Case
Amend Content	Change files in historical commits
Squash Commits	Combine multiple commits into one
Reword Message	Change commit message text
Update Tags	Move tags to new commits after rebase
Delete Branches	Remove local and remote branches
Force Push	Push rewritten history to remote

Workflow

Phase 1: ANALYZE

Gather current state before proposing changes.

# Current branch and HEAD
git rev-parse --abbrev-ref HEAD
git rev-parse --short HEAD

# Commit history
git log --oneline --decorate main

# All tags
git tag -l

# All branches
git branch -a -v

Phase 2: PLAN (DRY RUN)

OUTPUT FORMAT:

## DRY RUN - PROPOSED PLAN

### Current State
- Branch: {branch}
- HEAD: {sha}
- Commits: {count}
- Tags: {list}

### Operations
1. {operation description}
2. {operation description}
...

### Commands to Execute
{numbered list of exact commands}

### Risk Assessment
| Risk | Impact | Mitigation |
|------|--------|------------|

### Affected
- Commits: {list}
- Tags: {list}
- Remote: {yes/no force push required}

**Awaiting approval to proceed.**

Phase 3: CONFIRM

STOP AND WAIT for user to respond with approval (e.g., "OK", "proceed", "yes").

Phase 4: BACKUP

# Create backup branch
git branch backup/pre-rewrite-$(date +%Y%m%d-%H%M%S) HEAD

# Save tag messages to temp files
git tag -l --format='%(contents)' {tag} > /tmp/{tag}-message.txt

Phase 5: EXECUTE

Pattern A: Amend Content in Historical Commit