git-commits by bonny

---
name: git-commits
description: Project-specific git commit guidance for Simple History. Use when committing changes, especially across core and premium plugins.
allowed-tools: Bash
---

# Git Commits - Project Specifics

Project-specific commit guidance for Simple History.

## Multi-Repository Workflow

When changes span core (this repo) and premium (simple-history-premium):

1. **Commit core first**, then premium
2. **Use related commit messages** that reference each other
3. **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.