---

name: Git description: Complete Git version control workflow automation. USE WHEN user mentions commit, push, pull request, PR, branch, merge, rebase, stash, git status, staged files, unstaged changes, OR any version control operations. Handles conventional commits, security checks, and GitHub CLI integration.

Git

Complete Git version control workflow automation for Claude Code. This skill provides safe, structured workflows for all common git operations with built-in security checks, conventional commit support, and GitHub CLI integration.

Workflow Routing

When executing a workflow, output this notification:

CopyRunning the **WorkflowName** workflow from the **Git** skill...

Examples

Example 1: Stage and commit changes locally

CopyUser: "Commit these changes"
→ Invokes Commit workflow
→ Reviews all modified files for sensitive data
→ Generates conventional commit message
→ Stages and commits changes (NO push)
→ Returns commit hash and summary

Example 2: Full commit and push workflow

CopyUser: "Push my changes"
→ Invokes CommitPush workflow
→ Security scan for credentials/secrets
→ Generates descriptive commit message
→ Commits and pushes to remote
→ Confirms successful push with branch info

Example 3: Create a pull request

CopyUser: "Create a PR to main"
→ Invokes PullRequest workflow
→ Summarizes all commits in branch
→ Generates PR title and description
→ Uses GitHub CLI to create PR
→ Returns PR URL and details

Example 4: Check repository status

CopyUser: "What's the git status?"
→ Invokes Status workflow
→ Shows staged/unstaged/untracked files
→ Displays current branch info
→ Shows ahead/behind remote status

Example 5: Create worktree for parallel development

CopyUser: "Create a worktree for the hotfix"
→ Invokes Worktree workflow
→ Creates new worktree directory
→ Checks out branch in isolated directory
→ Returns worktree path and branch info
→ Preserves current work context

Security Protocols

CRITICAL: The following are NEVER committed:

Conventional Commits Reference

All commits follow Conventional Commits:

Commit Message Format:

Copy<type>(<scope>): <description>

[optional body]

[optional footer(s)]

Rules:

• Title under 70 characters
• Use imperative mood ("add" not "added")
• No period at end of title
• Body explains what and why, not how

Git Safety Rules

1. NEVER force push to main/master without explicit user confirmation
2. NEVER run destructive commands (git reset --hard, git clean -fd) without confirmation
3. ALWAYS check for uncommitted changes before switching branches
4. ALWAYS verify remote before pushing sensitive repos
5. NEVER skip pre-commit hooks unless explicitly requested
6. NEVER amend pushed commits without confirmation

AI Attribution Policy

DO NOT include AI attribution in commits:

• No "Generated with [Claude Code]" signatures
• No "Co-Authored-By: Claude" attributions
• No AI tool references in commit messages
• Create clean, professional commit messages

Tools

This skill uses standard git commands and optionally:

• GitHub CLI (gh): For PR creation and GitHub operations
• pre-commit: For validation hooks before commits

References

• references/ConventionalCommits.md - Detailed conventional commits guide
• references/GitBestPractices.md - Git workflow best practices
• references/GitWorktree.md - Git worktree concepts and command reference
• references/SecurityChecklist.md - Pre-commit security checklist