committinglisted

# Pre-commit / pre-push checklist Run before every commit and push, including the ones that look trivial. ## 0. Read the repo profile first This skill adapts to two axes declared in the repo's root `CLAUDE.md`, under a `## Repo profile` section, as literal tokens: - `Lock: locked` or `Lock: free` - `Docs language: en` or `Docs language: fr` Read them before doing anything else. If the section is missing, infer what you can (a "main is protected" note or a PR-only history points to `locked`; the README language points to the docs language), state your assumption, ask the owner to confirm once, then write the four-line `## Repo profile` marker into the root `CLAUDE.md` yourself so the next run is deterministic (the block is in the `scaffolding-repos` skill, step 5). Reach for the full `scaffolding-repos` skill only if the repo also lacks its other generic files. **Everything written for the owner follows the docs language** (commit messages, PR title and body, CHANGELOG entries, docs); only the conventional-commit prefixes stay English (`feat:`, `fix:`). Respect any markdown and punctuation rules the repo's `CLAUDE.md` sets (for example a ban on em-dashes in owner-facing text). ## 1. Git workflow rules Shared by both modes: - One commit per concern: one feature, one bugfix, one refactor. Never bundle unrelated changes in the same commit, because the owner relies on atomic commits to review and revert. - Conventional commits for messages (and PR titles when there is