Skill: Git Workflow
Description
Manages git operations following Gitflow strategy with conventional commits.
When to Use
- •Creating feature/fix/release branches
- •Committing code changes
- •Merging branches
- •Creating pull requests
Instructions
Branch Naming
- •Features:
feature/short-description - •Fixes:
fix/short-description - •Releases:
release/v1.0.0 - •Hotfixes:
hotfix/short-description
Commit Format
code
type(scope): description [optional body] [optional footer(s)]
Types: feat, fix, chore, docs, refactor, test, style, perf, ci
Workflow
- •Always branch from
develop(features/fixes) - •One logical change per commit
- •Write descriptive commit messages (what + why)
- •Keep commits atomic — each should compile and pass tests
- •Squash WIP commits before PR
PR Template
markdown
## What Brief description of changes. ## Why Context and motivation. ## How Technical approach taken. ## Testing How was this tested? ## Checklist - [ ] Tests pass - [ ] Lint clean - [ ] Types check - [ ] Docs updated (if needed)
Branch Protection Rules
- •
main: Protected. Only merge from release/hotfix branches. - •
develop: Protected. Only merge via PR with passing CI.