commitlisted

# Skill: commit **What it does.** Reads the working tree, infers a commit type and optional scope from what changed, proposes **one line**, and commits after the author approves it. **Triggers** - "commit" - "/commit" - "commit this", "commit the chapter" - Equivalent phrasing in the project's output language **Input.** Optional: what the author wants recorded, in their own words. **Output.** One commit, after explicit approval. > **Commit messages are written in English, always** — even when the book's output language is not. The types are the same vocabulary the skills use internally, and the log stays readable across projects. This is the one place in p10t where the output language does not apply. --- ## Core principle > **No skill commits on its own. This one only runs when the author asks for it.** A commit in a book repository is an assertion of authorship, and the log is the evidence base for `book-review.md` §3.5, which classifies each layer of the book as authorial, assisted, or generated-and-curated. If the machine writes its own history, that evidence becomes self-reporting. > **The second principle is narrower and does more work: stage only what the message describes.** > > That one binds the author too, and it is the rule that actually protects the workflow. See **The revision boundary** below. --- ## The convention ``` type(scope)!: subject ``` - `type` — from the closed list below - `(scope)` — optional; a chapter number, or a knowledge area (`wor