No ai traces
Keep delivered work free of AI self-reference, with no Co-Authored-By trailers or generated-with footers in commits and pull requests, and no comments, documentation, or changelog entries that narrate AI involvement, prompts, or the editing session. Use when writing commits, merge or squash messages, pull requests, release notes, changelogs, code comments, or documentation; do not use to bypass a policy that explicitly requires AI disclosure.From its SKILL.md
npx -y skills add 26zl/universal-agent-skills --skill no-ai-tracesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.0 KB, 307 tokens by cl100k_base, as published. Nobody here has run it
No AI Traces
Delivered work records the accountable human author and describes the change, never the tool or session that produced it.
Rules
- Never add a Co-Authored-By, Signed-off-by, or similar trailer naming an AI assistant, agent, model, or tool.
- Never append generated-with footers, robot signatures, tool names, or promotional links to commit messages, merge or squash messages, pull request titles or bodies, changelogs, or release notes.
- Never write code comments, docstrings, documentation, or ticket updates that narrate prompts, AI involvement, the editing session (including before/after or fix-history narration such as "previously… now…"), or a conversation with an assistant.
- Never change the configured Git author or committer identity.
- Preserve trailers and attribution that credit humans; only machine self-reference is removed or withheld.
- Do not introduce new attribution or narration while amending, rebasing, squashing, or rewording existing content.
- Keep AI mentions that are part of the product itself, its documented subject matter, or required third-party notices.
Boundaries
- An explicit user, repository, or organizational requirement to disclose AI use wins; disclose in the mandated form instead of applying this skill.
- Never remove attribution or sign-off lines that a policy, license, or developer certificate of origin requires.
- This skill governs text about tooling only; it never hides which changes were made or misrepresents review status.
What ships with it: 1 file
219 B alongside SKILL.md
agents/
- openai.yaml219 B
Gives 0 of the 12 instructions most readme changelog skills give in 307 tokens
Counted across 446 of the 460 authors here whose files we hold, read 2026-09-06
- Follow Keep a Changelog formatin 24 of 446
- Collect commits since the last git tagin 15 of 446, across 13 files
- Omit empty sectionsin 14 of 446
- Put breaking changes first with migration stepsin 14 of 446
- Include migration guidance for breaking changesin 11 of 446, across 10 files
- Categorize commits by conventional commit prefixin 11 of 446
- Mark breaking changes prominentlyin 10 of 446
- Prepend the new entry to CHANGELOG.mdin 9 of 446
- Highlight breaking changes with migration notesin 8 of 446, across 7 files
- Classify changes into Keep a Changelog categoriesin 8 of 446, across 7 files
- Group related commits into single entriesin 8 of 446
- Write the changelog from commitsin 8 of 446
Said here and by no other author read
- Record the accountable human author in delivered work
- Describe the change, not the tool or session
- Preserve attribution that credits humans
- Disclose AI use when policy mandates it
- Keep AI mentions that are part of the product
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.