Learn-skills.dev git-workflow

Git workflow expert. Use when managing branches, commits, merges, rebases, and release processes.

install

source · Clone the upstream repo

git clone https://github.com/NeverSight/learn-skills.dev

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/NeverSight/learn-skills.dev "$T" && mkdir -p ~/.claude/skills && cp -r "$T/data/skills-md/ai-engineer-agent/ai-engineer-skills/git-workflow" ~/.claude/skills/neversight-learn-skills-dev-git-workflow-493d17 && rm -rf "$T"

manifest: data/skills-md/ai-engineer-agent/ai-engineer-skills/git-workflow/SKILL.md

source content

Git Workflow

Execute git workflow action: $ARGUMENTS

Commit Messages

Follow Conventional Commits format:

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

[optional body]

[optional footer]

Types:

feat

fix

docs

style

refactor

perf

test

build

ci

chore

Common Workflows

Feature Branch

```
git checkout -b feat/<description>
```
from
```
main
```
Make changes with focused commits

Rebase on main before PR:

git fetch origin && git rebase origin/main

Push and create PR

Hotfix

```
git checkout -b fix/<description>
```
from
```
main
```
Make the fix with test
Push and create PR with priority label

Release

Update version in package files
Update CHANGELOG.md
Create release commit:
```
git commit -m "chore: release v1.2.3"
```
Tag:
```
git tag -a v1.2.3 -m "Release v1.2.3"
```
Push:
```
git push origin main --tags
```

Best Practices

Keep commits atomic — one logical change per commit
Write commit messages in imperative mood: "Add feature" not "Added feature"
Never force push to shared branches (main, develop)
Use
```
git rebase -i
```
to clean up local history before PR
Use
```
git stash
```
for temporary context switches
Review your own diff before committing:
```
git diff --staged
```
Use
```
.gitignore
```
for build artifacts, dependencies, secrets, IDE files