Skip to main content
Generalbendrucker

git

Git workflow and branching best practices. Use when working with git commands, creating branches, or pushing changes.

Stars
13
Source
bendrucker/claude
Updated
2026-05-31
Slug
bendrucker--claude--git
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/bendrucker/claude/HEAD/plugins/git/skills/git/SKILL.md -o .claude/skills/git.md

Drops the SKILL.md into .claude/skills/git.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

Git

  • Never git push to the default branch (usually main or master) unless I explicitly instruct you to do so.
  • Always use a topic branch with a few brief word hyphenated name

Commit Messages

For multi-line commit messages:

  • Simple (subject + body): Use multiple -m flags. Each -m creates a separate paragraph:
    git commit -m "Subject line" -m "Body paragraph here."
    
  • Complex: Use a heredoc to pass the message:
    git commit -m "$(cat <<'EOF'
    Subject line
    
    Body paragraph here.
    EOF
    )"