committinglisted

# Pre-commit / pre-push checklist Run before every commit and push, including the ones that look trivial. Steps 2 to 5 edit the worktree (comments, docs, `CLAUDE.md`, CHANGELOG), so run them before staging anything; step 1 holds the rules the commit and the push then follow. The other github skills point here for the shared rules (steps 0, 1, and 5) instead of restating them. These rules are defaults for the common case: when a repo's own conventions (its `CLAUDE.md`, its existing docs, its history) say otherwise, follow the repo. ## 0. Write in the repo's language Be consistent with what already exists: a repo whose README and docs are in French gets French commit messages, PR text, CHANGELOG bullets, and docs; an English repo gets English. If the root `CLAUDE.md` names a language, follow it. In a repo with nothing written yet, ask the owner once; when nobody can answer (an autonomous run, a scheduled task), write English and flag the assumption in your final report. Only the conventional-commit prefixes (`feat:`, `fix:`) and the CHANGELOG boilerplate and headings (step 5) stay English whatever the repo's language. Respect any other writing rules the repo's `CLAUDE.md` sets, such as a ban on em-dashes. ## 1. Git and GitHub rules - Commit on `main` and push. No feature branch and no pull request unless the owner asks for one or the repo requires it. If the push is rejected because the remote moved, `git pull --rebase --autostash` then push again (`--autostash` because ot