ai-commit-trailerslisted

# AI disclosure in commits The trailer answers "what made this", as opposed to `Co-authored-by`, which answers "who to ask about it" ## The rule ``` Generated-by: Claude Code:<model> # the task was carried out without the user's hand in it Assisted-by: Claude Code:<model> (mostly) # most of the final diff is mine, but they steered it Assisted-by: Claude Code:<model> (partly) # a substantial part is mine <no trailer> # the user's own work, mechanical, or dictated ``` The value is `<tool>:<model>` — the agent that made the change and the model actually running behind it; any harness names itself there. One trailer per commit: torn between two states, take the lower one, and where the case is genuinely unclear write a bare `Assisted-by`, which stays true of anything worth arguing about The trailer is content of the message, written into it deliberately, not a byline a tool appends: it belongs in the message's last block, beside any other trailer, with no blank line inside that block, because `git interpret-trailers` and `git log --format=%(trailers)` read that block and nothing above it ## Which state The test is whose answer a reviewer would get to "why is it done this way" — not who typed the lines | The user… | State | |---|---| | set the task, read the result, took it unchanged | `Generated-by` | | steered in prose — a direction, a rejected approach, "not like that, rather…" | `Assisted-by (mostly)` | | wrote or rewrote a