Overview
This skill covers the standard git workflow for developing features, fixing bugs, and managing code changes.
When to Use
- •Starting new feature work
- •Fixing bugs
- •Making code changes that should be tracked
- •Preparing code for review
Steps
- •
Check current status
bashgit status git branch
- •
Create feature branch (if not on one)
bashgit checkout -b feature/description
- •
Make changes incrementally
- •Small, focused commits
- •Clear commit messages explaining "why"
- •
Stage and commit
bashgit add <files> git commit -m "type: description Longer explanation if needed"
- •
Push and create PR
bashgit push -u origin feature/description
Watch Out For
- •Committing sensitive files (.env, credentials)
- •Large binary files
- •Committing unfinished work to main branch
- •Force pushing to shared branches
Commit Message Format
code
type: short description Longer description explaining why this change was made, not what was changed (the diff shows that). Refs: #123
Types: feat, fix, docs, style, refactor, test, chore