Git Workflow
Git workflow best practices including commit messages, branching strategies, pull requests, and collaboration patterns. Use when working with Git version control.
Install
npx skills add jefflester/claude-skills-supercharged --skill git-workflowgit clone --depth 1 https://github.com/jefflester/claude-skills-supercharged.git /tmp/claude-skills-supercharged
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills-supercharged/.claude/skills/git-workflow ~/.claude/skills/git-workflowPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Git Workflow Best Practices ## Purpose This skill provides guidance on Git workflow best practices to ensure clean commit history, effective collaboration, and maintainable version control in your projects. ## When to Use This Skill Auto-activates when: - Mentions of "git", "commit", "branch", "merge", "pull request" - Working with version control operations - Creating or reviewing commits - Managing branches and releases ## Commit Messages ### Conventional Commits Format Follow the Conventional Commits specification: ``` <type>(<scope>): <subject> <body> <footer> ``` **Types:** - `feat`: New feature - `fix`: Bug fix - `docs`: Documentation only - `style`: Code style changes (formatting, no logic change) - `refactor`: Code refactoring (no feature or bug fix) - `perf`: Performance improvements - `test`: Adding or updating tests - `build`: Build system or dependency changes - `ci`: CI/CD configuration changes - `chore`: Other changes (tooling, maintenance) **Examples:** ``` feat(auth): add OAuth2 authentication support Implement OAuth2 authentication flow using the authorization code grant type. Supports Google and GitHub providers. Closes #123 ``` ``` fix(api): handle null response from database query Previously, null responses would cause the API to crash. Now returns 404 with appropriate error message. Fixes #456 ``` ### Commit Message Best Practices 1. **Use imperative mood** in subject line: "Add feature" not "Added feature"
Details
- Skill name
git-workflow- Repository
- jefflester/claude-skills-supercharged
- Path
.claude/skills/git-workflow/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Git Workflow skill do?
Git workflow best practices including commit messages, branching strategies, pull requests, and collaboration patterns. Use when working with Git version control.
How do I install the Git Workflow skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jefflester/claude-skills-supercharged --skill git-workflow. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Git Workflow popular?
It lives in jefflester/claude-skills-supercharged, which has 43 GitHub stars and 3 forks.
Related skills
Skill Developer
43jefflester/claude-skills-supercharged
Create and manage Claude Code skills following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, keyword triggers, hook mechanisms (UserPromptSubmit), session tracking, and the 500-line rule.
API Security
43jefflester/claude-skills-supercharged
API security best practices and common vulnerability prevention. Enforces security checks for authentication, input validation, SQL injection, XSS, and OWASP Top 10 vulnerabilities. Use when building or modifying APIs.
Python Best Practices
43jefflester/claude-skills-supercharged
Python development best practices including PEP 8 style guidelines, type hints, docstring conventions, and common patterns. Use when writing or modifying Python code.
PR Description
49petekp/claude-code-setup
Write or update a GitHub PR description a teammate understands in one quick read: clear before/after behavior, useful visual evidence, and plain sentences grounded in the diff and real verification. Use when opening a PR or editing its description.
Regel Check
51neubauerwilli/gta6-skill
Der Regel-Check. Prüft jeden Clip gegen die Regeln der Kampagne (Länge, Wasserzeichen, Pflicht-Tags, Erwähnung, Plattform, Frist), bevor er rausgeht. Nutze ihn immer vor dem Posten, oder wenn der Nutzer sagt "prüf den Clip", "darf ich das posten", "Regeln checken" oder "ist der Clip okay".
PR Screenshot Comparison
49petekp/claude-code-setup
Create clear, polished before-and-after screenshots from the actual running product for a GitHub pull request. Use when a UI change needs visual proof: capture matching product states, crop to the relevant UI, stitch and caption one comparison image, attach it natively to the PR, and keep the image out of the repository.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.