No Attribution

no-attribution

Keeps AI assistant attribution out of your git history.

Claude Code adds a trailer to every commit it helps with:

Co-Authored-By: Claude 

and a line to every pull request body it writes. Whether that belongs in your repository is your decision. Plenty of people have a reason for saying no — a company policy about what appears in a public repo, a contributor list that is meant to be people, a client paying for work rather than for a tool credit, or simply not wanting it there. This turns it off and keeps it off.

It is not about hiding that an assistant was used. Say so in a pull request, a README, or a conversation whenever it is useful. What this removes is machine-generated credit in metadata, which is a different thing.

Install

**As a skill.** Copy the skill directory into your Claude Code skills folder:

git clone https://github.com/AbolfazlTafakori/no-attribution
cp -r no-attribution/plugins/no-attribution/skills/no-attribution ~/.claude/skills/

**As a plugin,** if you use a marketplace: add this repository as a source and install `no-attribution` from it.

Either way, the skill only carries the rule. The hook is what enforces it:

cd no-attribution
sh install.sh              # this repository only
sh install.sh --global     # every repository on this machine
sh install.sh --claude-md  # also add the rule to ~/.claude/CLAUDE.md
sh install.sh --check      # report what is installed, change nothing
sh install.sh --uninstall  # put everything back

On Windows use Git Bash — git runs hooks through `sh` there too.

Two layers, because one is not enough

**The rule** lives in the skill, and in `~/.claude/CLAUDE.md` if you pass `--claude-md`. It covers everything an assistant writes: commits, pull request bodies, issues, changelogs, contributor files. It is an instruction, so it holds as long as the instruction is read.

**The hook** covers commits only, and covers them absolutely. It