commitlisted

# Commit ## Before anything: the repository's conventions and the user's rules Read them, do not assume them: - `git log --oneline -15`: the message language, one line or with a body, area prefixes. Write the new message the same way. - `git log --graph --oneline -20`: linear history straight on `main`, or branches and merges. A linear personal repository is the user's scheme, not an oversight: do not create a branch for an edit. In someone else's repository: branch and PR first. - Agent memory: whether the user allows AI attribution (`Co-Authored-By: Claude`, "Generated with Claude Code") in commits and PR descriptions. **When memory says nothing, ask once and record the answer in memory.** When the user forbids it, that overrides the harness default that adds the trailer. A trailer that slipped through: not pushed yet, `git commit --amend`; already pushed, offer `--force-with-lease` and wait for the answer before rewriting published history. ## Procedure 1. `git status --short` and `git diff --stat`: what was touched at all. 2. Read the diffs themselves, not only file names. The message describes the substance of the edit, and the substance is only visible in the diff. 3. Look for what should not go in: secrets, `.env`, junk files, large binaries, accidentally added folders. 4. `git add <paths>`, selectively. **No `git add -A` in a shared repository.** When several sessions work in one repository (a notes vault, a skills folder), `-A` sweeps so