antwork-shiplisted
Install: claude install-skill polynode-co/antwork-skills
# Ship: from what you built to posts about it
The writing is the easy part. The judgment is the job: picking the two or three things worth a post out of a week of commits, telling them as a story instead of a changelog, and never claiming more than the code shows. Run the steps in order, and stop where the steps say stop.
## Arguments
`/antwork ship [--since <date|ref>] [--release <tag>] [--platforms linkedin,x,...] [--repo <path>]`
- **No range given:** everything since the most recent tag (`git describe --tags --abbrev=0`). If the repo has no tags, the last 7 days.
- **`--release <tag>`:** that release only: the tag's notes, plus the commits between the previous tag and it.
- **`--since`:** a date (`2026-10-01`), a ref (`v1.4.0`, a SHA) or a span (`14 days`).
- **`--platforms`:** limit the accounts. Without it, every connected account, confirmed in step 4.
- **`--repo`:** a path other than the current directory.
## 1. Read what happened (read-only)
From inside the repo, collect the window:
- `git log --no-merges --format='%h%x09%ad%x09%s%n%b' --date=short <range>` for the commits.
- If `gh` is available and the remote is GitHub: `gh pr list --state merged --search "merged:>=<start date>" --json number,title,body,mergedAt,labels,url` (a merged PR's title and body already say what changed in human words, so they beat raw commits) and `gh release view <tag> --json name,body,url` for a release.
- `git diff --stat <range>` for the scale of each change, when you need it.