Git workflow and branching best practices. Use when working with git commands, creating branches, or pushing changes.
Enforces git workflow best practices with topic branches and proper commit message formatting.
npx claudepluginhub bendrucker/claudeThis skill inherits all available tools. When active, it can use any tool Claude has access to.
git push to the default branch (usually main or master) unless I explicitly instruct you to do so.For multi-line commit messages:
-m flags. Each -m creates a separate paragraph:
git commit -m "Subject line" -m "Body paragraph here."
tmp/commit-msg.md, then git commit -F tmp/commit-msg.mdDo not use heredocs — they create temp files that fail in sandbox environments. This includes git commit -m "$(cat <<'EOF' ... EOF)" and cat > file << 'EOF'.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.