Publish Release (moi-computer)
Runbook wydania npm: lokalna weryfikacja, tag push, bramkowana publikacja CI, a następnie przywrócenie
Działa po konfiguracji
Co robi ten skill
Szczegółowy runbook wydania dla pakietu npm moi-computer: preflight on a clean main, a local verify pass that mirrors CI, version selection for next previews or stable, tag push into a reviewer-gated GitHub Actions publish, post-publish verification of dist-tags i provenance, i a restore phase that puts the dev link back. Uruchamia się na requests to publish, release, ship a version, or cut a dev preview inside that repo. Every command is hardcoded to that package i workflow, so elsewhere it reads as a template rather than a runnable skill.
Raport z testu
Queued here as publish-next; git history shows upstream deleted that path i the replacement, publish-release, now covers both next previews i stable releases. Ran its read-only phases live against a fresh clone: lint i format check clean, 708 tests pass, i bun pm pack produced a tarball with 70 dist/ entries i zero hits on its secrets scan. Its version rule earns its keep right now, because npm shows next at 0.4.1-next.0 while latest is 0.5.1, so both obvious no-skill answers sort below stable i would publish a preview containing older code than the release; the rule in the skill yields 0.5.2-next.0, which sorts above. I also reproduced the tar bug it documents: with two moi-computer-*.tgz files in the tree the unpinned glob makes tar treat the rest as members, i the dist/ count comes back 0 against a perfectly good tarball. The catch is scope - the package name, repo, release workflow i the hardcoded port 13059 are all baked in, so outside molefrog/moi this is something you rewrite, not something you run.
Testowano: 2026-07-29 · Claude Code 2.x (agent harness)
Instalacja
git clone https://github.com/molefrog/moi.git mkdir -p ~/.claude/skills cd moi && cp -r .agents/skills/publish-release ~/.claude/skills/publish-release
Komendy i przykładowe prompty
/publish-releaseRunbook wydania npm: lokalna weryfikacja, tag push, bramkowana publikacja CI, a następnie przywrócenie
Skille uruchamiają się na zwykłe polecenia — bez komend do zapamiętania. Po instalacji aktywują go prompty takie jak te (po angielsku):
Cut a next preview release of moi-computer from mainIs this repo in a publishable state, and what version should ship next?Ship v0.5.2 of moi-computer through the gated CI publish workflow