prepare-releaselisted

Use this skill whenever preparing agentsmesh for an npm release — whether first publish, patch, minor, or major. Triggers on: 'prepare release', 'ready to publish', 'ship version', 'release prep', 'get this to npm', 'bump version', 'cut a release', 'what's needed to publish'. Runs a strict ordered checklist: test suite health → timing hardening → CI/CD presence → community health files → changeset entry → package contents �� README badges → final gate → generate to targets. Releases are driven by changesets — never hand-edit `package.json` `version` or `CHANGELOG.md`. Do not skip phases or work from memory; execute every phase in order and fix gaps before moving on.
sampleXbro/agentsmesh · ★ 16 · AI & Automation · score 75

Install: claude install-skill sampleXbro/agentsmesh

## Purpose # Prepare Release You are acting as the release engineer for agentsmesh. Your job is to get the repo into a state that is safe, honest, and ready for `npm publish`. Work through each phase in order. Do not mark a phase complete until you have verified it, not just assumed it. ## Releases are changesets-driven — read this first Every user-facing change ships through a changeset. **Do not** hand-edit `package.json` `version` or `CHANGELOG.md` — both are generated by `changeset version` and any manual edit will be silently overwritten the next time the release PR rebases. The skill exists to make sure the changeset is honest, the CI gates are green, and the publish workflow is actually wired up. The flow: 1. All gates below pass locally. 2. A `.changeset/<slug>.md` file describes the change with a `patch | minor | major` bump and a user-facing summary. Commit it. 3. Push to `master` (or merge a feature branch into `master`). 4. `publish.yml` triggers — `changesets/action` detects the pending changeset and **opens a "chore: version packages" PR** that bumps `package.json` and rewrites `CHANGELOG.md`. 5. Review the version PR — confirm the bump and the rendered CHANGELOG section match intent. Edit the changeset summary or add a new changeset (then re-push) if the rendered output is wrong; never edit `package.json`/`CHANGELOG.md` directly on the version PR. 6. Merge the version PR → `publish.yml` runs again, sees no pending changesets, executes `pnpm release` (`pnp