- name
- git-manager
- description
- Advanced Git operations support for bisecting regressions, cleaning up branches, managing stash workflows, and analyzing commit/history state. Use when users ask for "git bisect", branch cleanup, stash recovery/organization, reflog or log analysis, or safe handling of destructive/history-rewriting commands.
git-manager
Summary
git-manager orchestrates advanced repository maintenance by combining bisecting, branch cleanup, stash handling, and log analysis into a cohesive guidance skill. It keeps teams safe by pairing every destructive recommendation with an explicit verification or rollback prompt before running commands that rewrite history.
Triggers
git managerbisect issuecleanup branchesstash helpanalyze git logsafe git ops
Workflow
- Assess repository health – start with
git status, reviewgit fetch --all, and record the current branch/tag. Prompt the user: _"Are we on the branch that should move forward, or is a temporary diagnostic branch mounted?"_ - Bisect troubleshooting – when isolating regressions, run
git bisect startwith the known good/bad commits and iteratively test. After each reproduce attempt, ask for confirmation beforegit bisect good/bad. Offer the safety reminder: _"Bisect rewrites HEAD; stash or commit open work first."_ - Branch cleanup – use
git branch --mergedversusgit branch --no-mergedto find stale branches. Recommendgit branch -d <branch>for merged work andgit branch -Donly after re-confirming the target branch via a safety prompt to avoid deleting active work. - Stash management – suggest
git stash list/git stash showto catalogue hidden work. Encourage naming stashes withgit stash push -m "description"and verify the exact entries beforegit stash drop/pop, reminding the user to keep a copy (git stash branch <name>) if they need extra safety. - Log analysis – guide through
git log --oneline --graph --decorate,git reflog, andgit log @{u}to understand recent operations. Offer commands likegit show <commit>for inspection and highlight the importance of reviewing commit messages before reverting or cherry-picking. - Safety prompts – before destructive commands (e.g.,
reset --hard,git clean -fd, branch deletion,rebase,push --force), run the two-step destructive confirmation protocol: (1) display the current branch name and HEAD commit hash or tag, verify the target commit, and remind the user to take a backup action (tag, temporary branch, stash, export patch, etc.); (2) require an explicit textualYESreply before running the command. Always pair the recommendation withgit status,git log -1, or agit tagsnapshot so the user can see exactly what would change, and prefergit push --force-with-leaseover--forceunless the situation explicitly warrants the risk.
Deliverables
- Provide step-by-step command sets for diagnostics (bisect, log review, stash recovery).
- Keep a safety checklist in every response: check HEAD, stash status, remote tracking state, and backup plan (tag or branch) before rewriting history.
- Offer follow-up summary: what was touched, what is stashed, and what commands to run next for cleanup.