ship-notelisted

Turn a thing you just shipped — a merged PR or a tagged release — into an announcement post that tells people what changed and why they should care. **You write the post** from the real diff and notes; capx never generates content, it only ships (each post passes the casserole guardrail at send). What to announce, if named: "$ARGUMENTS" If the account isn't connected yet, run the `connect` skill first, then come back. Follow these steps: 1. **Find the source.** From "$ARGUMENTS", identify the merged PR or release. If nothing's named, default to the most recent merge on this branch. - PR: `gh pr view <n-or-url> --json title,body,mergedAt,files,url` — and skim the actual change with `gh pr diff <n>` for anything non-obvious. - Release: `gh release view <tag> --json name,body,tagName,url`. - No `gh` / no URL? Fall back to `git log --oneline -10` and `git show <sha>` for the merge commit. Confirm it's actually **merged / published** — don't announce something still open or a draft tag. 2. **Extract the user-facing change.** Read past the internal churn (refactors, test scaffolding, bumps) to the *one thing a user or fellow dev actually gets*: a new capability, a fixed pain, a faster path, a breaking change they must act on. That — not the commit count — is the story. 3. **Draft the announcement.** Write ONE post (or a short thread if it genuinely needs it) that is: - **"We shipped X → here's what it means for you"** — lead with the change, then t