Skills

GIT Workflow

Guided git workflows: prepare PRs, clean up branches, resolve merge conflicts, handle...

Install

npx skills add jezweb/claude-skills --skill git-workflow -g -a claude-code -y
Repository
jezweb/claude-skills1.1k
Category
Git and review
Updated
26d ago
License
MIT
Context cost
Lightabout 884 tokens
Runs scripts
No, instructions only

What it does

Guided git workflows: prepare PRs, clean up branches, resolve merge conflicts, handle monorepo tags, squash-and-merge patterns. Use when asked to prepare a PR, clean branches, resolve conflicts, or tag a release.

Git Workflow

Guided workflows for common git operations that benefit from structured steps.

PR Preparation

When preparing a pull request:

  1. Gather context

    • git log main..HEAD --oneline, list all commits on the branch
    • git diff main...HEAD --stat, see all changed files
    • git status, check for uncommitted work
  2. Draft PR content

    • Title: under 70 chars, describes the change (not the branch name)
    • Body: summarise the "why", list key changes, add test plan
    • Use the commit history to write the summary, don't rely on memory
  3. Push and create

    git push -u origin HEAD
    gh pr create --title "..." --body "$(cat <<'EOF'
    ## Summary
    - ...
    
    ## Test plan
    - [ ] ...
    
    šŸ¤– Generated with [Claude Code](https://claude.com/claude-code)
    EOF
    )"
    
  4. Verify, gh pr view --web to open in browser

Branch Cleanup

Clean up merged branches safely:

  1. Switch to main and pull latest

    git checkout main && git pull
    
  2. List merged branches (excludes main/master/develop)

    git branch --merged main | grep -vE '^\*|main|master|develop'
    
  3. Delete local merged branches

    git branch --merged main | grep -vE '^\*|main|master|develop' | xargs -r git branch -d
    
  4. Prune remote tracking refs

    git fetch --prune
    
  5. List remote branches with no local tracking (optional)

    git branch -r --merged origin/main | grep -vE 'main|master|develop|HEAD'
    

Merge Conflict Resolution

When a PR has conflicts:

  1. Assess the conflict scope
    git fetch origin
    git merge origin/main --no-commit --no-ff
    git diff --name-only --diff-filter=U  # List conflicted files
    
Read the whole SKILL.md on GitHub

More in Git and review