# Master Advanced Git Workflows

Advanced Git work can rewrite history, lose changes, or disrupt shared branches. This skill provides structured workflows, safety checks, and recovery steps for complex repository tasks.

## Install

```bash
npx skillstore add sickn33/git-advanced-workflows
```

## Metadata

- Status: approved
- Slug: sickn33-git-advanced-workflows
- Skillstore revision: r2
- Version status: missing
- Tree hash: 374f1da72c8bd4daeb54887d49059beb01b58d0f6c1c60a68750b41f70b2e1bf
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/git-advanced-workflows
- Ref: 88a8e9a07f4c54ab105c1c41b6267c287146b07b
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, filesystem
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/sickn33-git-advanced-workflows
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-git-advanced-workflows/manifest

## Capabilities

- Explains interactive rebase actions for reordering, combining, editing, or dropping commits.
- Guides single, ranged, and staged cherry-pick workflows across branches.
- Uses manual or automated Git bisect workflows to identify a regression commit.
- Organizes parallel branch development with Git worktrees and cleanup steps.
- Shows reflog-based recovery for deleted branches, lost commits, and mistaken resets.
- Compares rebase and merge strategies for local, shared, and release branches.

## Use Cases

- Prepare a Reviewable Feature Branch: Create a safe plan to squash fixups, reorder commits, and update a pull request without overwriting collaborators.
- Trace a Regression: Plan a manual or isolated automated bisect between known good and bad revisions.
- Recover Repository Work: Use reflog evidence to restore commits or branches after a mistaken reset, deletion, or history edit.

## Prompt Templates

### Inspect My Branch Safely

```
Review my current Git branch state and explain safe next steps. Start with read-only checks and do not change files or history.
```

### Plan a Clean Pull Request

```
Plan how to clean commits on [feature branch] before merging into [base branch]. Identify shared commits and request confirmation before rewriting history.
```

### Design a Regression Bisect

```
Design a bisect between [good revision] and [bad revision]. Explain the test signal and isolate any historical scripts before execution.
```

### Recover From a Git Mistake

```
Analyze this reflog and repository status: [details]. Propose the least destructive recovery, preserve current work, and include verification and rollback steps.
```

## Limitations

- It provides guidance but cannot guarantee repository state, permissions, or remote branch policies.
- Referenced supporting files and scripts are not included in this package.
- Examples use placeholder branches, commits, paths, versions, and test commands.
- Destructive commands require independent review, backups, and explicit confirmation.

## Best Practices

- Inspect status, recent history, remotes, and branch sharing before changing commits.
- Create a backup reference and define rollback steps before destructive or history-rewriting operations.
- Run tests and compare the resulting branch against its base before pushing.

## Anti Patterns

- Do not rebase or force push a shared branch without explicit coordination.
- Do not run historical repository scripts with secrets, broad permissions, or unrestricted network access.
- Do not use hard reset until current changes are reviewed, preserved, or intentionally discarded.

## Security Audit

- Audited at: 2026-07-23T23:31:28.832\+00:00
- Summary: All 48 static alerts are false positives caused by Markdown formatting, fixed command substitution, or intentional Git worktree paths. Semantic review found real operational risks from destructive resets, remote history rewriting, and test execution across historical revisions. No prompt injection or malicious intent was found.

## Stats

- Views: 118
- Downloads: 12
- Favorites: 0
- Popularity score: 0