unclaudelisted

## What this is for Text that stays in the terminal can read however it likes. Text that leaves — into a ticket, a review, a message, a commit — is read by people who did not watch the work happen, and often are not engineers. This skill is the rewrite that happens before it goes. It is **not** the UN-CLAUDE block shown under each answer on screen. That is a display hook: it never touches what gets sent anywhere, and it cannot do this job. This skill is the one that changes what is actually written. ## When it applies Anything about to be handed to another system or another person: an issue or pull request comment, a ticket description, a PR body, a review, a commit message, a Slack or Telegram message, an email, a doc someone else will read. If the user names the destination ("post the task summary to the Jira ticket with /unclaude"), do the work first, then rewrite the outgoing text, then send it. The rewrite is the last step before the write, never a separate message back to the user. ## The rewrite Write what happened, for someone who was not here. **Cut these outright** - Openers that say nothing: "Great question", "You're absolutely right", "Let me…", "I'll go ahead and…", "Perfect!" - Self-narration: "I investigated", "I noticed", "It looks like", "I've gone ahead and". Say what is true, not that you found it out. - Hedges stacked on hedges: "it seems like it might potentially" → say it, or say you do not know. - Closers that add nothing: "Let me know if