ship-release
/ship-release
Wydaje nową wersję projektu: podbija manifesty, aktualizuje CHANGELOG, taguje, tworzy release na GitHub i publikuje na npm.
- Autor
- joezhuo2 ↗
- Repozytorium
- ship-release-skill ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 12.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 12.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Wydaje nową wersję projektu: podbija manifesty, aktualizuje CHANGELOG, taguje, tworzy release na GitHub i publikuje na npm.
Wyzwalacze z opisu
Argumenty
/ship-release [version | patch | minor | major]
Oryginalny opis (EN)
Use when the user asks to release, ship, publish, cut or tag a version of a project ("release v0.2.0", "ship a patch", "bump and publish"). Bumps every version manifest, updates CHANGELOG and README badges, commits, lands it directly or through a pull request (pre-PR check, conflict fixes, merge, worktree cleanup), tags, creates the GitHub release, and publishes to or verifies npm.
Jak działa
- 1. Pick the version
- 2. Preflight
- 3. Bump every manifest
- 4. Changelog
- 5. README
- 6. Check, then confirm
- 7. Commit, land, tag
- 8. GitHub release
- 9. npm
- 10. Clean up worktrees
Podgląd SKILL.md
---
name: ship-release
description: Use when the user asks to release, ship, publish, cut or tag a version of a project ("release v0.2.0", "ship a patch", "bump and publish"). Bumps every version manifest, updates CHANGELOG and README badges, commits, lands it directly or through a pull request (pre-PR check, conflict fixes, merge, worktree cleanup), tags, creates the GitHub release, and publishes to or verifies npm.
argument-hint: "[version | patch | minor | major]"
---
# ship-release
Release the current project end to end. Requested version or bump: $ARGUMENTS
Run the steps in order. Stop and report as soon as a step fails; never skip ahead.
## 1. Pick the version
- Last release: `git describe --tags --abbrev=0` (no tag yet means this is the first release; use the manifest version).
- If the user gave a version or `patch` / `minor` / `major`, use it.
- Otherwise propose one from `git log <last-tag>..HEAD --oneline`: breaking change is major (minor while on 0.x), new feature is minor, anything else is patch. Ask once.
- Keep the repo's tag style (`v1.2.3` or `1.2.3`), taken from the existing tags. Default `v`.
## 2. Preflight
All of these must pass before any file changes:
- `git status --porcelain` is clean, or holds only changes meant for this release. Ask about anything else.
- After `git fetch`, you are on the default branch and not behind its upstream. On any other branch, or in a linked worktree (`git worktree list`), the release goes through the PR route in step 7.
- Save the `git worktree list` output. Step 10 uses it to tell your worktrees from the user's.
- The tag does not exist: `git tag -l <tag>` and `git ls-remote --tags origin <tag>` are both empty.
- `gh auth status` succeeds.
- If `package.json` exists and is not `"private": true`: `npm whoami` succeeds and `npm view <name>@<version> version` finds nothing.
- The project's tests pass (`npm test`, or whatever the README or CI uses).
## 3. Bump every manifest
Find every place the old version lives:
```bash
git grep -nF "<old-version>" -- . ':!CHANGELOG.md' ':!*lock*'
```
Usual places:
| File | How |
|------|-----|
| `package.json`, `package-lock.json` | `npm version <new> --no-git-tag-version` |
| `.claude-plugin/plugin.json` | `version` |
| `.claude-plugin/marketplace.json` | `version` of each plugin entry, if present |
| `pyproject.toml`, `setup.py`, `__version__` | edit |
| `Cargo.toml` | edit, then `cargo check` to refresh `Cargo.lock` |
| `manifest.json`, version constants in source | edit |
Read each grep hit before changing it: bump the project's own version, not a dependency that happens to share the number. Run the grep again afterwards; every remaining hit needs a reason.
## 4. Changelog
- Follow the format the file already uses. If there is no `CHANGELOG.md`, create one in Keep a Changelog format.
- Add `## [<new>] - <YYYY-MM-DD>` above the previous release, built from `git log <last-tag>..HEAD`.
- Group as Added / Changed / Fixed. Write what changed for the user, not commit subjects. Leave out version bumps and merge commits.
- If there is an `[Unreleased]` section, move its entries into the new section and leave the heading empty.
- Update the compare links at the bottom if the file has them.
## 5. README
- Dynamic badges (`img.shields.io/npm/v/...`, `github/v/release/...`) update themselves. Leave them.
- Update hardcoded versions: static badges (`badge/version-1.2.3-...`), install lines pinned to `@1.2.3` or `#v1.2.3`, "current version" text.
- If the release adds a command, option or install step the README does not mention, add it.
## 6. Check, then confirm
- Run the tests again.
- npm package: `npm pack --dry-run` and read the file list. No secrets, no missing files.
- `git diff --stat` and read the diff for secrets (tokens, `.env`, keys).
- Show the user the version, the changed files and the new changelog section. Ask once before step 7, unless they already told you to release without asking. Everything after this point is public and cannot be undone.
## 7. Commit, land, tag
Stage only the release files. Use the message style of earlier release commits (`git log --oneline -20`); default `Release v<new>`.
Pick one route to get the commit onto the default branch:
- **Direct:** you are on the default branch, it is not protected and the repo does not release through PRs. `git push origin <branch>`.
- **PR:** anything else. Follow the PR route below.
Then tag the commit that is on the default branch: `git tag -a <tag> -m "<tag>"` and `git push origin <tag>`. Never `--tags`, never `--force`.
### PR route
1. **Branch.** If you are on the default branch, `git switch -c release/v<new>` before committing. Otherwise keep the branch you are on.
2. **Pre-PR check.** All must pass before the push:
- `git fetch origin`, then `git merge origin/<default>`. Resolve conflicts as in step 4 below.
- `git diff origin/<default>...HEAD --stat` lists only files meant for this release. Read the diff for secrets and leftover debug code.
- The tests pass on the merged result.
- `gh pr list --head <branch>` shows no open PR for this branch. If one exists, reuse it.
3. **Open the PR.** `git push -u origin <branch>`, then `gh pr create --base <default> --title "Release v<new>" --body-file <file>` with the new changelog section as the body.
4. **Fix conflicts.** `gh pr view --json mergeable,mergeStateStatus`. If it reports `CONFLICTING`:
- `git fetch origin && git merge origin/<default>`. Never rebase or force-push a pushed branch.
- Version manifests take the new version. In the changelog, keep the entries from both sides, the new section on top.
- In code, keep the intent of both sides. If you cannot tell what the other side meant, stop and ask.
- Run the tests, commit the merge, push.
5. **Checks.** `gh pr checks --watch`. If one fails, read `gh run view --log-failed`, fix, push, and watch again.
6. **Merge.** Use the method earlier PRs used (`gh pr list --state merged --limit 5 --json mergeCommit,title`); default `gh pr merge --squash --delete-branch`. In a linked worktree leave out `--delete-branch` and run `git push origin --delete <branch>` afterwards. If a review is required, stop and ask the user for it. Never `--admin`.
7. **Sync.** In the main checkout: `git switch <default>` and `git pull --ff-only`. This is the commit to tag. Worktree cleanup happens in step 10.
## 8. GitHub release
Read `.github/workflows/` first.
- A workflow that runs on tag push and creates the release: do not create one yourself. `gh run watch` it, then `gh release view <tag>`.
- Otherwise: write the new changelog section to a temp file and run `gh release create <tag> --title <tag> --notes-file <file> --verify-tag`. Add `--prerelease` for `-rc`, `-beta` or `-alpha` versions.
## 9. npm
Skip if there is no `package.json` or it is private.
- A workflow that runs `npm publish`: wait for it instead of publishing yourself.
- Otherwise `npm publish` from the tagged commit. Add `--access public` for a scoped package's first publish and `--tag next` for prereleases.
- If npm asks for a one-time password or browser login, stop and ask the user to run `npm publish` themselves. Never ask for or type their password or token.
- Verify: `npm view <name>@<new> version` prints the version. The registry can lag; retry for up to a minute. Then check `npm view <name> dist-tags.latest`.
## 10. Clean up worktrees
Delete every worktree you created in this session: those missing from the list saved in step 2, and any you made or entered earlier in the conversation. Leave the user's worktrees alone.
Run `git worktree list` from the main checkout. For each of yours:
- `git worktree remove <path>`. No `--force`: if git refuses, show the user the files left in it and ask.
- `git branch -d <branch>`. After a squash merge git refuses; confirm `gh pr view <number> --json state` says `MERGED`, then use `-D`. Never delete an unmerged branch without asking.
- If the remote branch is still there and its PR is merged, `git push origin --delete <branch>`.
Finish with `git worktree prune` and run `git worktree list` again; only the user's worktrees should remain.
## 11. Report
Give the version, the tag, the release URL, the npm URL, the worktrees removed, and anything skipped, failed or not verified.
## When something goes wrong
- Before the push: fix it and amend freely.
- After the push: never move or delete a pushed tag, never force-push, never `npm unpublish`. Fix forward with a patch release.
- PR merged but not tagged: tag the merge commit on the default branch and carry on from there. Do not open a second PR.
- Tag pushed but `npm publish` failed: fix the cause and publish again from the tagged commit. Do not retag.
- Release workflow failed: read `gh run view --log-failed`, fix forward, and tell the user what state the tag, the release and the registry are in.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · joezhuo2/ship-release-skill | 100 | MIT |
| hyodotdev/openiap | 90 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 3857e3b713b0 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 2 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100release
Generuje changelog z commitów, podbija wersję, tworzy release na GitHubie i publikuje pakiet w npm. - 100release
Wydaje CLI scratch lub paczkę pi: podbija wersję, taguje, tworzy release na GitHubie, a CI publikuje w npm. - 100release
Wydaje moduł Magento 2: podbija wersję, aktualizuje CHANGELOG, waliduje, taguje i tworzy notatki z commitów. - 100release
Wydaje wtyczkę project-with-reflect dla opiekuna repozytorium: podbija wersję, changelog, tag i GitHub release. - 100release-workflow
Wydaje Atom-lite na npm i GitHub: sprawdza bramki, zapisuje zmiany w changelogu, taguje i weryfikuje publikację. - 100ship
Przeprowadza wydanie od początku do końca: podbija wersję wszędzie, pisze changelog i dokumentację, taguje, publikuje na PyPI i npm.