writing-commitslisted

# writing-commits This skill produces git commits that match the m3l-automation Conventional Commits standard exactly — from picking the right type to deciding whether a body is worth writing. The goal is to make every commit self-explanatory to a reviewer who wasn't in the room. ## Checklist (copy-paste before drafting) - [ ] Read `git diff --staged` — understand every changed file - [ ] Pick the type from the table in Step 2 (when in doubt, `chore:` for tooling; `feat:` for a new public symbol) - [ ] Draft a subject ≤ 70 chars, imperative, lowercase after `type:` - [ ] Decide body: needed for `feat:` / `fix:` / non-obvious `chore:`; omit for mechanical chores - [ ] Add `Co-Authored-By:` footer when Claude authored the commit - [ ] Add `BREAKING CHANGE:` footer for `feat!:` commits - [ ] Run `git commit -m "..."` with the full message ## Step 1 — Understand the change ```bash git diff --staged # the files about to be committed git diff # unstaged context (reference only) git log main...HEAD --oneline # commits already on this branch ``` Read all three outputs before drafting anything. The staged diff is the source of truth; the log prevents duplicate subjects when multiple commits are planned. ## Step 2 — Select the commit type | Type | Use when | Public-API impact | | ----------- | ------------------------------------------------------- | ----------------- | | `feat:` |