git-version-controllisted

# Git Version Control <skill_scope skill="git-version-control"> **Related skills:** - `software-engineer` — Design principles that inform commit granularity - `test-driven-development` — Test-commit cycles and when to commit during TDD This skill covers Git commit standards, branch strategy, and LLM-assisted development workflows. It emphasizes atomic commits, meaningful commit messages, and high-frequency integration. </skill_scope> ## Core Philosophy <core_philosophy> **"Commit Often, Perfect Later, Publish Once"** — Seth Robertson **Integration frequency is the most powerful determinant of branching success.** Elite teams integrate multiple times daily. "If it hurts, do it more often." — Martin Fowler **Revertability principle**: Commits should represent meaningful units of work that could be reverted independently without breaking the system. </core_philosophy> ## Commit Practices <atomic_commits> **Atomic commit decision:** "If you can describe what you did in a short sentence and it makes sense, commit." **When larger commits are acceptable:** Initial prototyping (squash before review), closely coupled changes, when over-granularity loses context. **Time guideline:** 30-60 min ideal, max 4 hours. See `<commit_triggers>` for event-based commit points. </atomic_commits> ### Commit Triggers <commit_triggers> **Commits are responses to completion events, not scheduled activities.** Commit discipline isn't about remembering to commit—it's about recognizing compl