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.

aksuharun 172623f 4 files · 8.6 KB Updated

File contents

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 — The 7 rules for great commit messages. Read when writing, reviewing, or advising on commit messages.
  • 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 — Flat, descriptive branch naming guidance. Read when creating or reviewing branch names.

aksuharun/skills/tree/main/git-best-practices commit 172623f977

Frequently asked questions

npx skillmds@latest add aksuharun/git-best-practices