Skip to content
Skills Library
Programming · Automation

create-release

/create-release

Plans the release commits, writes Changesets notes, applies them to the changelog and version, creates the git tag, and pushes that commit and tag. Use when the user names /create-release or asks to release this repo. Does not publish a package.

Author
ploau ↗
Licence
MIT
Last repository change
30.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 30.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Plans the release commits, writes Changesets notes, applies them to the changelog and version, creates the git tag, and pushes that commit and tag. Use when the user names /create-release or asks to release this repo. Does not publish a package.

Original author description

Plans the release commits, writes Changesets notes, applies them to the changelog and version, creates the git tag, and pushes that commit and tag. Use when the user names /create-release or asks to release this repo. Does not publish a package.

How it works

  1. User language
  2. Plan
  3. Notes
  4. Version
  5. Tag
  6. After
Original SKILL.md headings · 62 lines, 462 words
SKILL.md preview
---
name: create-release
description: Plans the release commits, writes Changesets notes, applies them to the changelog and version, creates the git tag, and pushes that commit and tag. Use when the user names /create-release or asks to release this repo. Does not publish a package.
disable-model-invocation: true
---
![create-release](thumb.png)

## User language

Chat replies, and the prose of any report this skill writes, use the user's language. Infer that language from the conversation, or from the text after the command. Keep each paragraph of that output in one language. When this skill names a heading that another skill has to find, keep that heading text as specified and write the body in the user's language. The instructions in this file stay in English.

# Create release

Release this repository. The text after the command is also a language signal. Invoking `/create-release` authorizes the commits below, one git tag, and the push of those commits and that tag. It does not authorize a force push, a git config change, or a package publish.

Run from the git root that contains `.changeset/config.json`. If that file is missing, stop. Stay on the branch being released. Do not open a feature branch for the version commit.

Follow [git-plan](../git-plan/SKILL.md) for every commit. Pass the author and committer with `git -c` on each commit. Do not write git config. One domain per commit. Title only, technical English, at most 72 characters. Do not hand-edit `version` in `package.json`.

## Plan

List the commits in this order. Product commits come first and must not touch `version` or `CHANGELOG.md`. The note commit contains only new `.changeset/*.md` files. The version commit contains only what `npm run version` changed.

```text
<type>(<scope>): <short message>
chore(changeset): note <what shipped>
chore(release): version X.Y.Z
```

Secrets, lockfiles that the version command did not change, and unrelated dirty files stay out. Say why.

## Notes

Pending notes are the `.md` files in `.changeset/` other than `README.md`. If none describe what is about to ship, write one. The package name is `name` in the root `package.json`. Pick patch, minor, or major from what shipped since the last `CHANGELOG.md` section. The body is the release note, not a copy of `git log`.

Commit only those new note files:

```text
chore(changeset): note <what shipped>
```

## Version

1. Run `npm run version` from the repo root. It consumes the pending notes, updates `CHANGELOG.md`, and sets `version` in `package.json`.
2. Read the new version. The tag is `v` plus that version.
3. You may polish the generated changelog prose. Do not edit `version` by hand.
4. Commit only the files that command changed:

```text
chore(release): version X.Y.Z
```

## Tag

Run `npx changeset git-tag`. Confirm `vX.Y.Z` exists locally. If the package is already tagged, stop and do not push.

```bash
git push origin HEAD
git push origin vX.Y.Z
```

Do not use `--force` or `--tags`. Do not run `changeset publish`.

## After

Report the version, the commit hashes, the tag, and the remote branch. If the push fails, leave the local commit and tag in place and quote the error.
Files in this package (2)
  • SKILL.md 3 KB
  • thumb.png 23 KB

Versions

RepositoryScoreLicence
This page · ploau/engineering-skills100MIT
cocoindex-io/cocoindex100Apache-2.0
yandex/implicits100Apache-2.0
richkuo/rk-skills100MIT
ragnarok22/agent-skills100MIT

Database snapshot: 13.11.2026 · package version ca9e4799cb81 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 2 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100gh-tag-release
    Date the changelog and push a release tag to trigger publish CI. Differs from gh-draft-release, which drafts a GitHub Release with notes. Args: none required. Use when the user asks to tag a release, publish a version, or mentions /gh-tag-release.
  • 100ac-release
    Release workflow: branch, changelog, PR, tag, GH release. Triggers on keywords: release, create release, publish release, tag release
  • 100chamoji-release
    Cut a release from git history in one command with the chamoji CLI. It picks the semver bump from the commits, adds the CHANGELOG.md section, bumps manifest versions, and makes the release commit and tag (and pushes plus a GitHub release on request). Use it whenever the user…
  • 100changelog
    Write release notes or a CHANGELOG.md entry from git history. Use when the user says "write the changelog", "release notes for v2.3", "what changed since the last release/tag", or is preparing a release or version bump.
  • 100release
    Cut a new release: group Conventional Commits since the last tag, append a CHANGELOG section, create a release commit, and add an annotated git tag. TRIGGER when the user says "cut a release", "tag a release", "release v1.2.0", "ship version 1.2.0", "create a release for 1.2.0",…
  • 100release
    Plan version scope, verify release integrity (commit↔CHANGELOG, tag↔artifacts), generate changelogs, and run full releases. Use when cutting a release or bumping a version. Trigger on "cut a release", "bump the version", "generate changelog", "release plan", "verify the release".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.