Git Manager

Advanced Git operations support for bisecting regressions, cleaning up branches, managing stash workflows, and analyzing commit/history state. Use when users...

Security Scan

The skill's instructions match its name and description (advanced Git operations) and request no unexpected credentials or installs, though it assumes git is available and will propose destructive repo commands guarded by explicit confirmation steps.

Purpose & Capability

The name/description and SKILL.md consistently focus on bisecting, branch cleanup, stash management, and log/reflog analysis. There are no unrelated environment variables, config paths, or external endpoints requested. One minor mismatch: the skill expects the git binary to be present (it repeatedly instructs running git commands) but the registry metadata lists no required binaries.

Instruction Scope

Instructions are narrowly scoped to repository operations (git status, fetch, bisect, branch deletion, stash operations, reset/clean, push). The skill explicitly requires two-step confirmation before destructive actions and recommends backups (tags/temporary branches/stashes). It does not instruct reading unrelated system files or exfiltrating data. Note: because it directs running commands that affect the working tree/remote, those commands will operate on local files and may trigger network operations (push/pull) using local credential helpers.

Install Mechanism

No install spec and no code files — instruction-only skill. This is low-risk from an installation perspective because nothing is downloaded or written to disk by an installer.

Credentials

The skill requests no environment variables or secrets. This matches its purpose. Caveat: running git push or other network commands will use whatever Git credentials/credential-helper are configured on the host; the skill itself does not request or expose additional credentials.

Persistence & Privilege

always:false and no persistence or config writes. The skill can be invoked autonomously by the agent (default), which is normal — but because it suggests destructive git operations, autonomous execution without user confirmation would be risky; the SKILL.md explicitly requires user YES confirmations before destructive steps.

Assessment

This skill appears coherent and limited to Git operations, but it assumes git is installed and will propose destructive commands (branch -D, reset --hard, clean -fd, force-push). Before installing: 1) ensure you run it only in repositories where you can safely test; 2) keep automatic/autonomous invocation disabled or ensure the agent enforces the documented two-step confirmation; 3) be aware pushes will use your local Git credentials (the skill doesn't request secrets); and 4) test in a non-critical clone or sandbox to confirm behavior and prompts before using on important repos.

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 manager
• bisect issue
• cleanup branches
• stash help
• analyze git log
• safe git ops

Workflow

1. Assess repository health – start with git status, review git 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?"
2. Bisect troubleshooting – when isolating regressions, run git bisect start with the known good/bad commits and iteratively test. After each reproduce attempt, ask for confirmation before git bisect good/bad. Offer the safety reminder: "Bisect rewrites HEAD; stash or commit open work first."
3. Branch cleanup – use git branch --merged versus git branch --no-merged to find stale branches. Recommend git branch -d <branch> for merged work and git branch -D only after re-confirming the target branch via a safety prompt to avoid deleting active work.
4. Stash management – suggest git stash list/git stash show to catalogue hidden work. Encourage naming stashes with git stash push -m "description" and verify the exact entries before git stash drop/pop, reminding the user to keep a copy (git stash branch <name>) if they need extra safety.
5. Log analysis – guide through git log --oneline --graph --decorate, git reflog, and git log @{u} to understand recent operations. Offer commands like git show <commit> for inspection and highlight the importance of reviewing commit messages before reverting or cherry-picking.
6. 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 textual YES reply before running the command. Always pair the recommendation with git status, git log -1, or a git tag snapshot so the user can see exactly what would change, and prefer git push --force-with-lease over --force unless 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.