npm-releaselisted
Install: claude install-skill lamberto15/turboship
# npm release
Releases should be boring: a contributor adds a changeset to their PR, a bot keeps a "Version
Packages" PR up to date, and merging that PR publishes to npm from CI, with no token to leak and a
provenance attestation that proves the package was built from this repo. Nothing is published from
a laptop after the very first version.
This skill builds on **package-ci** (pnpm, Biome, `verify` script, `.github/actions/setup`,
Dependabot) and the **github-actions** rules and scripts (`../github-actions/scripts/`). If any part
of package-ci's setup is missing, add it first, including `.github/dependabot.yml` with a cooldown:
pinned action SHAs in the release workflow go stale without it.
**This skill never runs `publish` itself.** Publishing is irreversible and belongs to the maintainer
(first release) and to CI (every release after). It prepares everything and hands over a checklist.
## Workflow
### 0. Preflight: can the planned names be published? (before generating any file)
A scope that turns out to be taken costs a rename of every reference afterwards (package names,
imports, docs, CI scripts). npm users and orgs share **one namespace**: a scope can be owned by a
user account with zero packages, and https://www.npmjs.com/org/<name> then silently redirects to
`/~<name>`, so "create the organisation" is where it fails. Check every planned name first:
```bash
# scope (@<scope>/...): 404 {"error":"Scope not found"} = free; 200 = owned by a user OR an org
curl -s