← ClaudeAtlas

ai-commit-trailerslisted

AI disclosure and submission safety for commits, pushes, issues, pull requests, PR reviews, comments, and discussions: Assisted-by / Generated-by trailers, upstream requirements, and mandatory user review before publishing. Use before any commit or action that publishes content as the user, when writing or reviewing a CONTRIBUTING/AI policy, before contributing to a third-party repo, when AI contribution rules are unclear, or when asked about Co-authored-by / Signed-off-by / Generated-by. Triggers: commit, push, pull request, issue, PR review, comment, Assisted-by, Generated-by, Co-authored-by, Signed-off-by, закоммить, коммит, запушь, пуш, открой PR, пулреквест, открой ишью, оставь комментарий, ответь в ишью, ревью PR, смёрджи, раскрытие ИИ, подпись коммита
rokokol/ai-commit-trailers-skill · ★ 0 · Code & Development · score 75
Install: claude install-skill rokokol/ai-commit-trailers-skill
# AI disclosure in repository contributions For commits, the trailer answers "what made this", as opposed to `Co-authored-by`, which answers "who to ask about it". The safety rules below also apply to pushes, issues, pull requests, reviews, comments, discussions, and any other action performed under the user's identity. Keep the rule itself in whatever file your agent always reads; this one holds the reasoning behind it, the upstream texts it rests on, and the template ## Before sending anything as the user Never push, open or update an issue or pull request, submit a review, post a comment or discussion, or perform another externally visible action under the user's identity without a final, explicit confirmation immediately before the action 1. Show the user exactly what will be published, including the destination and all relevant metadata. For a push, include the ref and commits; for an issue, pull request, review, comment, or discussion, include the exact title and body as applicable 2. Explicitly ask the user to review it personally. Do not describe tool output, tests, or an agent's review as a substitute for their own inspection 3. Ask whether to proceed, and wait for an unambiguous approval. A request made earlier in the task is not the final approval required by this rule Do not batch approval for multiple submissions. If the content or destination changes after approval, show the revised payload and ask again Local commits are the narrow exception: apply the di