tag-auditlisted

# Tag Audit — triage accumulated safety tags Stacked-rebase sessions accumulate safety tags fast — each surgical operation deserves its own rollback anchor, but the cost of regret is high. Once an operation is validated and pushed, those tags decay into redundancy: they either duplicate another tag, point at the same SHA as a current branch ref, or mark an intermediate waypoint no one will ever `git reset` back to. This skill audits the safety-tag namespace, surfaces duplicates by sorting on SHA (not name), proposes deletions with reasons, and deletes only after explicit confirmation. ## When to Use - After a successful + pushed + CI-green stacked-rebase or surgical-fix session, when the operation's safety tags are no longer load-bearing. - When `/stack-cascade` Step 2 refuses to proceed because the `OP_ID` namespace is non-empty. - When `git tag -l 'safety/*' 'pre-*' 'post-*'` returns more entries than feels healthy and you want to know which ones still earn their keep. - When inheriting a workspace from a past session and the tag namespace is unfamiliar. ## When NOT to Use - During an in-flight cascade or surgical fix — tags are still load-bearing rollback anchors. - When the operation hasn't been validated end-to-end (CI green, PRs reviewed, no surprises from teammates) — the rollback window is still open. - On release tags or other semantically-meaningful tags outside the safety-tag pattern set — narrow the pattern set first. ## The Survivor Heurist