Commit Assisted-by trailer

Commit Assisted-by trailer

Record the assisting agent's involvement in a commit by adding an Assisted-by: <agent-name>/<model-id> git trailer. The <agent-name> identify the specific AI assistant (CLI/harness) and <model-id> is the LLM version that contributed to the commit. This disclosure provides transparency about AI involvement in code changes.

In the command examples below, substitute <agent-name>/<model-id> with your own values before running anything.

Mode 1 — commits you create yourself

When you create a commit in a session, limit the commit subject to 50 characters. Use the imperative mood in the subject line (e.g., "Add support for X" instead of "Added support for X").

If the commit message body is needed to explain what and why, wrap it at 72 characters. Avoid verbose explanations in the body, be as concise as possible while still conveying the necessary information.

Pass --trailer directly on the commit command. This is the clean path and avoids amend noise:

git commit -s -m "Add support for X" --trailer "Assisted-by: <agent-name>/<model-id>"

Note that all commits must be signed off with a real human name and email to meet the DCO requirement. Never use your agent's name or a pseudonym in the sign-off or co-author fields.

Mode 2 — commits that appear outside your own git commit invocations

Sometimes a commit lands on HEAD that you did not run yourself — the user invoked git via a shell escape (e.g. Claude Code's ! git commit ...) or a separate terminal. Your only window is after the fact.

Run the bundled safety-check script before amending. It prints safe, or skip:<reason> if HEAD is already pushed, already trailered, a merge, or has a rebase/cherry-pick/revert/bisect in progress.

Invoke it with the script's full path — resolve scripts/safety-check.sh against the directory this SKILL.md was loaded from, not the current working directory (the two are almost never the same):

<skill-dir>/scripts/safety-check.sh