← ClaudeAtlas

git-graphlisted

Visualize git branch history as an ASCII graph. Shows branch topology, merge points, tags, and recent commit messages. Use when orienting to branch structure, reviewing merge history, or understanding divergence points.
mherod/swiz · ★ 3 · Code & Development · score 62
Install: claude install-skill mherod/swiz
Render the git branch graph for the current repository and explain the topology: active branches, merge points, divergences, and tags. ## Usage - `/git-graph` (defaults: last 30 commits, all branches) - `/git-graph 50` (last 50 commits) - `/git-graph 20 main` (last 20 commits on main only) ## Context - Current directory: !`pwd` - Current branch: !`git branch --show-current` - Branch limit: !`echo "${1:-30}"` - Branch filter: !`echo "${2:---all}"` - Graph: !`git log --graph --oneline --decorate ${2:---all} -${1:-30} 2>/dev/null` - All local branches: !`git branch -v 2>/dev/null` - Remote tracking branches: !`git branch -rv 2>/dev/null | head -20` - Tags (recent): !`git tag --sort=-creatordate 2>/dev/null | head -10` - Unpushed commits: !`git log origin/$(git branch --show-current)..HEAD --oneline 2>/dev/null || echo "(no upstream)"` ## Your Task Present the branch graph clearly and annotate key topology features. **DO:** - Display the raw graph output from Context verbatim in a code block first - Identify the current HEAD position and active branch - Call out merge commits and what branches they merged - Highlight divergence points (where branches split from a common ancestor) - Note any tags and what they mark - Flag unpushed commits on the current branch - Identify long-running branches vs short-lived feature branches - Note if the graph shows clean linear history vs complex merge topology **DO NOT:** - Re-run git commands already provided in Context — use the captur