# Git Best Practices

> Git best practices for commit messages and branch workflow. Use when writing or reviewing commit messages, advising on branching, merging, rebasing, PRs, or keeping a clean linear history.

- Skill: `aksuharun/git-best-practices` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add aksuharun/git-best-practices`
- Raw SKILL.md: https://api.skillmd.com/api/skills/aksuharun/git-best-practices/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: aksuharun (https://skillmd.com/u/aksuharun)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/aksuharun/git-best-practices

---


# Git Best Practices

Three core areas:

1. **Commit messages** — how to write clear, meaningful commit messages
2. **Branch workflow** — how to keep a clean, linear history using rebase
3. **Branch naming** — how to name branches clearly without noisy prefixes

Read the relevant reference file(s) before advising.

## References

- **[references/commit-messages.md](references/commit-messages.md)** — The 7 rules for great commit messages. Read when writing, reviewing, or advising on commit messages.
- **[references/git-workflow.md](references/git-workflow.md)** — Rebase-first branch workflow for clean history. Read when advising on branching strategy, PRs, merging, or conflict resolution.
- **[references/branch-naming.md](references/branch-naming.md)** — Flat, descriptive branch naming guidance. Read when creating or reviewing branch names.