commitlisted

## Context Before proposing anything, run these and read the output in full: ``` git status git diff HEAD # staged + unstaged; use --cached when staging exists git branch --show-current git log --oneline -10 # match the existing message style ``` ## Commit message format ``` <type>[optional (scope)]: <description> [optional body] <Assisted by <model version>> ``` ### Types | Type | When to use | |----------|-------------------------------------------------| | `feat` | New user-facing feature or capability | | `fix` | Bug fix or correcting broken behavior | | `ui` | Visual/layout changes | | `refact` | Code restructure without changing behavior | | `docs` | Documentation, references, specs, product plans | | `content`| Case-study copy or assets — `src/content/`, images, video | | `perf` | Performance improvement | | `chore` | Maintenance — deps, config, cleanup | ### Rules 1. **One logical change per commit.** Group or split by topic — multiple types/scopes = multiple commits. 2. **Imperative present tense**: "add", "fix", "update" — not "added", "fixes", "updated". 3. **Description under 72 characters.** Lead with what changed, not which files. 4. **Scope is optional** — use when it clarifies: `ui(profile):`, `fix(auth):`, `feat(directions):`. 5. **Body bullets start with file name** — e.g. `- tags.py: a