Handles the end-to-end release process for Tailwind Stash, including versioning and publishing.

Install

mkdir -p .claude/skills/release-beumerr && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12023" && unzip -o skill.zip -d .claude/skills/release-beumerr && rm skill.zip

Installs to .claude/skills/release-beumerr

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Prepare and publish a release for Tailwind Stash. Bumps the version, generates changelog entries, runs all checks, and publishes via GitHub Release.
148 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Bump the version number in package.json
  • Generate changelog entries from git history
  • Run quality checks (format, lint, typecheck, test)
  • Create a commit with a release message
  • Tag, push, and create a GitHub Release

How it works

This skill reads the current version and changelog, prompts for release type, calculates the new version, updates files, runs quality checks, and then commits and publishes the release.

Inputs & outputs

You give it
Git repository with package.json and CHANGELOG.md
You get back
New version in package.json, updated CHANGELOG.md, release commit, and GitHub Release

When to use release

  • Publish new project release
  • Generate automated changelog
  • Bump version and tag repository

About this skill

Prepare and publish a release for Tailwind Stash.

Steps

  1. Verify the working tree is clean and on the master branch.
  2. Read the current version from package.json and the latest entry in CHANGELOG.md.
  3. Ask what type of release this is: patch, minor, or major.
  4. Calculate the new version number based on the current version and release type.
  5. Update package.json with the new version.
  6. Update CHANGELOG.md:
    • Add a new ## [x.y.z] - YYYY-MM-DD section with today's date.
    • Look at the git log since the last tag to generate the changelog entries, grouped by Added/Changed/Fixed/Removed as appropriate.
    • If there is an [Unreleased] section, move its content into the new version section and leave [Unreleased] empty.
  7. Run npm run format to format the changed files.
  8. Run npm run lint, npm run typecheck, and npm test to verify everything passes.
  9. Show a summary of the changes and ask for confirmation before committing.
  10. After confirmation, create a commit with message release: vX.Y.Z.
  11. Run npm run release to tag, push, and create the GitHub Release.

Rules

  • Must be on master branch with a clean working tree before starting.
  • Never skip quality checks.
  • Always show the changelog diff before committing.
  • Stop and ask if any check fails.

When not to use it

  • When not on the master branch
  • When quality checks are intended to be skipped

Limitations

  • Requires being on the master branch
  • Requires a clean working tree
  • Cannot skip quality checks

How it compares

This workflow automates version bumping, changelog generation, and release publishing, ensuring all checks pass before a release.

Compared to similar skills

release side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
release (this skill)05moNo flagsIntermediate
flow-nexus-platform64moReviewBeginner
netlify-deploy76moReviewBeginner
azure-static-web-apps47moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry