affaan-m/everything-claude-code/git-workflow
- community
Checking that the SKILL.md file is still in the repository.
Git workflow patterns including branching strategies, commit conventions, keeping history clean and readable, tidying local commits before merging, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes. Use when choosing a branching strategy, writing commit conventions, cleaning up history before a pull request, deciding merge versus rebase, or resolving conflicts.
Install
npx vskill@latest install affaan-m/everything-claude-code/git-workflowSKILL.md
Git Workflow Patterns
Best practices for Git version control, branching strategies, and collaborative development.
When to Activate
- Setting up Git workflow for a new project
- Deciding on branching strategy (GitFlow, trunk-based, GitHub flow)
- Writing commit messages and PR descriptions
- Resolving merge conflicts
- Managing releases and version tags
- Onboarding new team members to Git practices
Branching Strategies
GitHub Flow (Simple, Recommended for Most)
Best for continuous deployment and small-to-medium teams.
Rules:
mainis always deployable- Create feature branches from
main - Open Pull Request when ready for review
- After approval and CI passes, merge to
main - Deploy immediately after merge
Trunk-Based Development (High-Velocity Teams)
Best for teams with strong CI/CD and feature flags.
Rules:
- Everyone commits to
mainor very short-lived branches - Feature flags hide incomplete work
- CI must pass before merge
- Deploy multiple times per day
GitFlow (Complex, Release-Cycle Driven)
Best for scheduled releases and enterprise projects.
Rules:
maincontains production-ready code onlydevelopis the integration branch- Feature branches from
develop, merge back todevelop - Release branches from
develop, merge tomainanddevelop - Hotfix branches from
main, merge to bothmainanddevelop
When to Use Which
| Strategy | Team Size | Release Cadence | Best For | |
|---|---|---|---|---|
| GitHub Flow | Any | Continuous | SaaS, web apps, startups | |
| Trunk-Based | 5+ experienced | Multiple/day | High-velocity teams, feature flags | |
| GitFlow | 10+ | Scheduled | Enterprise, regulated industries |
Commit Messages
Conventional Commits Format
Types
| Type | Use For | Example | |
|---|---|---|---|
feat | New feature | feat(auth): add OAuth2 login | |
fix | Bug fix | fix(api): handle null response in user endpoint | |
docs | Documentation | docs(readme): update installation instructions | |
style | Formatting, no code change | style: fix indentation in login component | |
refactor | Code refactoring | refactor(db): extract connection pool to module | |
test | Adding/updating tests | test(auth): add unit tests for token validation | |
chore | Maintenance tasks | chore(deps): update dependencies | |
perf | Performance improvement | perf(query): add index to users table | |
ci | CI/CD changes | ci: add PostgreSQL service to test workflow | |
revert | Revert previous commit | revert: revert "feat(auth): add OAuth2 login" |
Good vs Bad Examples
Commit Message Template
Create .gitmessage in repo root:
Enable with: git config commit.template .gitmessage
Merge vs Rebase
Merge (Preserves History)
Use when:
- Merging feature branches into
main - You want to preserve exact history
- Multiple people worked on the branch
- The branch has been pushed and others may have based work on it
Rebase (Linear History)
Use when:
- Updating your local feature branch with latest
main - You want a linear, clean history
- The branch is local-only (not pushed)
- You're the only one working on the branch
Rebase Workflow
When NOT to Rebase
Pull Request Workflow
PR Title Format
PR Description Template
Code Review Checklist
For Reviewers:
- [ ] Does the code solve the stated problem?
- [ ] Are there any edge cases not handled?
- [ ] Is the code readable and maintainable?
- [ ] Are there sufficient tests?
- [ ] Are there security concerns?
- [ ] Is the commit history clean (squashed if needed)?
For Authors:
- [ ] Self-review completed before requesting review
- [ ] CI passes (tests, lint, typecheck)
- [ ] PR size is reasonable (<500 lines ideal)
- [ ] Related to a single feature/fix
- [ ] Description clearly explains the change
Conflict Resolution
Identify Conflicts
Resolve Conflicts
Conflict Prevention Strategies
Branch Management
Naming Conventions
Branch Cleanup
Stash Workflow
Release Management
Semantic Versioning
Creating Releases
Changelog Generation
Git Configuration
Essential Configs
Useful Aliases
Gitignore Patterns
Common Workflows
Starting a New Feature
Updating a PR with New Changes
Syncing Fork with Upstream
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 96 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/git-workflow/SKILL.md
Popularity
- Repository stars
- 170,070
- Repository forks
- 26,350
- Repository npm downloads, 7 days
- 1,425
- 7-day trend score
- 78
Stars and forks are for the whole GitHub repository, not this skill alone. Downloads are for the repository's npm package. Refreshed 28 Apr 2026, 5 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/affaan-m/everything-claude-code/git-workflow)