القائمة
Use when adding a changeset to a PR, deciding whether a PR needs one, cutting or debugging a release, or when the Version PR / npm publish flow looks wrong.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | release-and-changesets |
| description | Use when adding a changeset to a PR, deciding whether a PR needs one, cutting or debugging a release, or when the Version PR / npm publish flow looks wrong. |
fixed lockstep group
in .changeset/config.json; the repo is in pre-release alpha mode via
.changeset/pre.json).patch while in alpha.Create one with pnpm changeset (select all packages, patch) or write the
file by hand under .changeset/ following an existing one.
main.changeset publish or npm publish yourself.vX.Y.Z-alpha.N) and a consolidated GitHub Release are created by
the workflow.npm@latest once broke every release via an engines bump). Do not
"simplify" it back to latest..changeset/*.md files and delete them in a cleanup PR.latest dist-tag for the unscoped packages is managed manually
after publishes; a publish alone does not move it.Use when writing or debugging Nextly integration tests (*.integration.test.ts), when integration tests fail with self-import or connection errors, or when adding database-backed test coverage for a new feature.
Use when adding a new field type to Nextly (a new entry in the FieldType union, a new field factory, or a new schema-builder picker type), or when a field type renders or stores incorrectly across the config, catalog, column-mapping, or admin layers.
Use when reviewing a Nextly pull request, responding to review-bot feedback (CodeRabbit, Greptile), or preparing a PR to pass review.