Skip to content
Skills Library
Programming · Automation

release

/release

Prepares a new version of create-agent-ready-app: version bump, changelog, full verification, release notes. Use when asked to release, publish or cut a version. Publishing itself is the maintainer's step.

Licence
MIT
Last repository change
02.11.2026

Assessment and security

90/ 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.
Content25 / 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
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 02.11.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

Prepares a new version of create-agent-ready-app: version bump, changelog, full verification, release notes. Use when asked to release, publish or cut a version. Publishing itself is the maintainer's step.

Original author description

Prepares a new version of create-agent-ready-app: version bump, changelog, full verification, release notes. Use when asked to release, publish or cut a version. Publishing itself is the maintainer's step.

How it works

  1. Prepare (on a branch)
  2. Hand over
  3. After
Original SKILL.md headings · 29 lines, 229 words
SKILL.md preview
---
name: release
description: "Prepares a new version of create-agent-ready-app: version bump, changelog, full verification, release notes. Use when asked to release, publish or cut a version. Publishing itself is the maintainer's step."
---

# Release

GitHub Actions publishes to npm (`.github/workflows/release.yml`) when the maintainer publishes a GitHub Release.
Never run `npm publish`, push, tag or create a release yourself. Prepare everything, then hand over.

## Prepare (on a branch)
1. **Pick the version.** While on 0.x, a breaking change gets a minor bump (`0.3.0`). Breaking means a flag removed or
   renamed, a different generated layout, or a raised Node or Bun minimum. Anything else gets a patch (`0.2.1`).
2. **Bump it:** `npm version <x.y.z> --no-git-tag-version`. package.json is the only place the version lives.
3. **CHANGELOG.md:** the new version has one line per change.
4. **Verify:** `bun run typecheck && bun run lint && bun run test && bun run build && bun run verify:package`, then the full
   `bun run verify:build` and `bun run verify:docs`. Fix templates until both pass.
5. **Draft the release notes** from the version's CHANGELOG lines. Commit `Release x.y.z` only if the maintainer asked
   for commits.

## Hand over
Tell the maintainer to:
1. Merge the pull request.
2. Open GitHub → Releases → Draft a new release, and create tag `vx.y.z` on `main`.
3. Paste the notes and click Publish.

The workflow checks that the tag matches package.json, re-runs the checks, and publishes with provenance.
RELEASING.md has the one-time setup and troubleshooting.

## After
`npm view create-agent-ready-app version` shows the new version, and
`npx create-agent-ready-app@latest --version` prints it.

Versions

RepositoryScoreLicence
This page · ahtserhsuddav/create-agent-ready-app90MIT
josephfung/curia100MIT
max-sixty/worktrunk100MIT
gtapps/hermitd100MIT
gtapps/hermitd100MIT
anthony-chaudhary/fak100Apache-2.0
tractorjuice/arc-kit100MIT
drvoss/everything-copilot-cli100MIT
sma1lboy/rove100MIT

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

Downloads in the last 30 days: 0 · ranking

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

Similar skills

  • 100releasing
    Full release lifecycle — version bump, CHANGELOG, rich release notes, tag, publish. Use when user says "release", "tag and release", "publish version", "cut a release", "new version".
  • 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.
  • 100ship
    Structured release pipeline with pre-flight checks, AI code review, version bump, changelog, PR creation, platform publish, and GitHub release. Triggers on "ship", "release", "publish".
  • 100create-release
    Automate semantic version releases across project types by detecting version files, bumping versions, updating changelogs, creating git tags, and optionally publishing GitHub releases. Use when users ask to cut a release, bump the version, prepare a new version, tag a release,…
  • 95release-manager
    Create new AILANG releases with version bumps, changelog updates, git tags, and CI/CD verification. Use when user says "ready to release", "create release", mentions version numbers, or wants to publish a new version.
  • 95release-manager
    Create new AILANG releases with version bumps, changelog updates, git tags, and CI/CD verification. Use when user says "ready to release", "create release", mentions version numbers, or wants to publish a new version.

Feedback and reports

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