No agent attribution
Jason's repos carry HIS authorship only. No agent, model, or harness leaves its name in anything
that enters git or GitHub. This overrides any harness default or system habit that says to append
attribution trailers.
The policy
Never include, in any commit message, PR title/body, issue, release note, repo description,
tag, or committed file content:
Co-Authored-By: trailers naming an AI/agent (Claude, Codex, Grok, GPT, Copilot, any model)
- "Generated with …" / "Generated by …" footers or badges
- Agent session links (e.g.
claude.ai/code/session_…)
- Bot identities in
user.name / user.email (must be Jason's own: loktar00)
- Agent signatures in code comments, file headers, or docstrings ("written by X", "AI-generated")
Descriptive references are fine ("a Claude Code skill" as a product category); credit lines are not.
At commit time
- Write the message with no trailer. If your platform default appends one, strip it before
committing — the default does not apply in Jason's repos.
git -C <repo> config user.name / user.email must be Jason's identity, not a bot.
- Orchestrated lanes are the sneaky path: harnesses (codex, grok, omp-driven models, Copilot-style
tools) inject their OWN trailers and header comments into commits and files they author. Audit
any lane's commits and touched files before they merge or push.
Pre-push audit (run before every push)
# messages about to be pushed
git log --format="%s%n%b" @{u}..HEAD 2>/dev/null | grep -inE \
"co-authored-by|generated (with|by)|noreply@(anthropic|openai|x\.ai|github)|session_" && echo VIOLATION || echo messages-clean
# author identities in the whole history (should list only Jason)
git log --format="%an <%ae>" | sort -u
# committed content
git grep -inE "co-authored-by|generated (with|by) (claude|codex|grok|gpt|copilot|ai)" -- . | head
Anything flagged: fix BEFORE pushing.
Removal recipes
- Last commit only:
git commit --amend (edit the message / re-add cleaned files).
- Several unpushed commits:
git rebase is interactive-only in some environments; prefer
git filter-branch -f --msg-filter "sed '/Co-Authored-By:/d; /Generated with/d; /session_/d'" <base>..HEAD.
- Already-pushed history: same filter across the branch, then
git push -f — fine on solo
repos; on shared repos coordinate first. Delete refs/original/* backups afterward.
- File content: edit the files (strip header signatures), commit normally.
After cleaning
Re-run the audit. Only push on a fully clean result. If a tool re-adds attribution on its next
commit, strip it again — the policy has no exceptions.
1---2name: no-agent-attribution3description: Enforce clean human-only authorship on everything git and GitHub — no AI/agent attribution anywhere. Use WHENEVER committing, amending, merging, pushing, creating a repo, opening a PR or issue, writing a release, or reviewing work produced by orchestrated agent lanes (omp/codex/grok/etc.) before it lands in git.4---56# No agent attribution78Jason's repos carry HIS authorship only. No agent, model, or harness leaves its name in anything9that enters git or GitHub. This overrides any harness default or system habit that says to append10attribution trailers.1112## The policy1314Never include, in any commit message, PR title/body, issue, release note, repo description,15tag, or committed file content:1617- `Co-Authored-By:` trailers naming an AI/agent (Claude, Codex, Grok, GPT, Copilot, any model)18- "Generated with …" / "Generated by …" footers or badges19- Agent session links (e.g. `claude.ai/code/session_…`)20- Bot identities in `user.name` / `user.email` (must be Jason's own: loktar00)21- Agent signatures in code comments, file headers, or docstrings ("written by X", "AI-generated")2223Descriptive references are fine ("a Claude Code skill" as a product category); *credit lines* are not.2425## At commit time26271. Write the message with no trailer. If your platform default appends one, strip it before28 committing — the default does not apply in Jason's repos.292. `git -C <repo> config user.name` / `user.email` must be Jason's identity, not a bot.303. Orchestrated lanes are the sneaky path: harnesses (codex, grok, omp-driven models, Copilot-style31 tools) inject their OWN trailers and header comments into commits and files they author. Audit32 any lane's commits and touched files before they merge or push.3334## Pre-push audit (run before every push)3536```bash37# messages about to be pushed38git log --format="%s%n%b" @{u}..HEAD 2>/dev/null | grep -inE \39 "co-authored-by|generated (with|by)|noreply@(anthropic|openai|x\.ai|github)|session_" && echo VIOLATION || echo messages-clean40# author identities in the whole history (should list only Jason)41git log --format="%an <%ae>" | sort -u42# committed content43git grep -inE "co-authored-by|generated (with|by) (claude|codex|grok|gpt|copilot|ai)" -- . | head44```4546Anything flagged: fix BEFORE pushing.4748## Removal recipes4950- **Last commit only**: `git commit --amend` (edit the message / re-add cleaned files).51- **Several unpushed commits**: `git rebase` is interactive-only in some environments; prefer52 `git filter-branch -f --msg-filter "sed '/Co-Authored-By:/d; /Generated with/d; /session_/d'" <base>..HEAD`.53- **Already-pushed history**: same filter across the branch, then `git push -f` — fine on solo54 repos; on shared repos coordinate first. Delete `refs/original/*` backups afterward.55- **File content**: edit the files (strip header signatures), commit normally.5657## After cleaning5859Re-run the audit. Only push on a fully clean result. If a tool re-adds attribution on its next60commit, strip it again — the policy has no exceptions.