commit-changeslisted
Install: claude install-skill wardawgmalvicious/claude-plugins
# Commit workflow
Turn the current working-tree changes into one or more well-formed
commits. Committing only — pushing, amending, rebasing, and tagging
happen only when explicitly requested, never as follow-through.
## Survey first
1. `git status --short` — full picture of modified, renamed, untracked.
Note anything **already staged that you did not stage**.
2. `git log --oneline -10` — calibrate message style against this
repo's actual history, not assumptions.
3. Read the diffs (`git diff`, `git diff --stat`, plus untracked
files) well enough to explain *why* each change exists, not just
what it touches. Never commit content you haven't looked at.
4. **On `main`? Branch when the work is more than one commit, or an
intermediate state would break while deployed**, named
`<type>/<kebab-slug>`, a [type](#messages) and 2–4 words naming the
subject, where the user's instructions name no other form — and from
the first commit when it is bound for `land-branch`, which refuses
to start from `main`. Work in a repo that lands by pull request is
bound for `land-branch`: a pull-request rule on `main`
(`land-branch` step 7 has the two reads), or `(#<n>)` and
`Merge pull request` subjects in the log above; a fast-forward
landing leaves none. A repo's own
committed convention wins, in its `CONTRIBUTING.md` or agent
instructions: one that commits straight to `main` answers *no*, and
then you commit where you stand. Say which way you went.