diff --git a/.claude/skills/audit/SKILL.md b/.claude/skills/audit/SKILL.md
index 68296d1..cf3902e 100644
--- a/.claude/skills/audit/SKILL.md
+++ b/.claude/skills/audit/SKILL.md
@@ -229,6 +229,7 @@ After the final tier, give a brief summary: what was applied, what was backlogge
 - Dump every tier at once or rely on a single big report. Walk tier by tier so the user only has to track one decision at a time.
 - Surface phase numbers/names to the user. Phases are scaffolding for this skill, not vocabulary the user should have to learn.
 - Auto-apply changes that affect public API surface even after a generic "go ahead". If a finding touches `pub` items, lift it into the Needs discussion tier before presenting.
+- Reference the audit run itself in commit titles or bodies (no "from audit", "audit cleanup", "via /audit", "found by audit"). Commits should describe the change, not how it surfaced. The audit is the trigger, not the subject.
 - Stack findings from multiple lenses into one commit without clear grouping.
 - Invent findings to fill space if a lens comes up empty. "Nothing to flag" is a valid outcome and should be reported as such.
 - Re-raise items already in `TODO.md` / `BACKLOG.md`.