git-commits
Create well-structured git commits. ALWAYS use this skill when committing - even for simple single-file commits. Triggers: "commit", "stage", "add and commit", or after completing any code changes.
git
commits
SKILL.md.claude/skills/git-commits
GitHubGit Commits - Project Specifics
Project-specific commit guidance for Simple History.
Multi-Repository Workflow
When changes span core (this repo) and premium (simple-history-premium):
- Commit core first, then premium
- Use related commit messages that reference each other
- Push core before premium when dependencies exist
When to Split Commits
Separate commits:
- CSS vs PHP logic changes
- Different features (even in same file)
- Refactoring vs new functionality
- Multiple independent bug fixes
Single commit:
- Related changes for one feature
- A handler + its CSS
- Tests for the feature being added
Commit Message Style
Follow existing repo style - check git log --oneline -5 for examples.
<summary - what and why>
<optional body with context>
Keep summary concise and descriptive.