Skills Guide

Release Tailwind Stash

VerifiedCaution

Prepare and publish a release for Tailwind Stash, automating version bump, changelog, checks, and GitHub release.

Download and use
Sby Skills Guide Bot
DevOpsIntermediate
7/22/2026
Claude Code
#release-management#changelog#versioning#npm#git

Recommended for

Backend developerClaude CodeDevOps engineerGit automation

Automated summary

Automates preparing and publishing a release for the Tailwind Stash project: version bump, changelog entries, quality checks, and a GitHub Release.

Strengths

  • Walks through the full release sequence end to end: version, changelog, formatting, lint, typecheck, tests, commit, tag, and publish
  • Builds the changelog from the git log since the last tag, grouped into Added/Changed/Fixed/Removed
  • Enforces guardrails: clean tree, master branch, stop on failing checks, confirmation before committing
  • Shows the changelog diff before committing, making review explicit

Limitations

  • Tightly coupled to the Tailwind Stash repo: npm run format/lint/typecheck/test/release scripts and the master branch are hard-coded
  • Assumes the release tooling (tag, push, GitHub Release) is already configured in the project
  • No rollback procedure is described if the push or GitHub Release creation fails
  • Model invocation is disabled, so the skill must be triggered explicitly by the user
When to use it

Use it when you need to ship a new Tailwind Stash version with a changelog and full verification.

When not to use it

Avoid it on a different repository, on a feature branch, or before the project's npm release scripts exist.

Security analysis

Caution
Quality score88/100

The skill is a legitimate release workflow, but it invokes npm scripts and git/GitHub publishing operations, so it has meaningful execution and external side-effect risk. There is no evidence of obfuscation, destructive commands, or secret exfiltration, so it is best classified as caution rather than risky.

Findings
  • •Executes repository-defined npm scripts (`format`, `lint`, `typecheck`, `test`, `release`) which can run arbitrary project code.
  • •Performs git commit/push and creates a GitHub Release, producing external side effects.
  • •Requires shell/git/npm/network access despite no allowed-tools being declared.
How this analysis is made

Examples

Patch release
Prepare a patch release for Tailwind Stash and show me the changelog diff before committing.
Minor release with review
Cut a minor release: bump the version, generate the changelog from the git log since the last tag, run all checks, and wait for my confirmation before committing.
Pre-release sanity check
Run the release steps up to the quality checks for a major version bump, but stop before committing so I can review the changelog.

name: release description: Prepare and publish a release for Tailwind Stash. Bumps the version, generates changelog entries, runs all checks, and publishes via GitHub Release. disable-model-invocation: true

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.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/release-tailwind-stash-mrwak9dn/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/release-tailwind-stash-mrwak9dn' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/release-tailwind-stash-mrwak9dn/download' --output '.skill-downloads/release-tailwind-stash-mrwak9dn/SKILL.md.part' && mv '.skill-downloads/release-tailwind-stash-mrwak9dn/SKILL.md.part' '.skill-downloads/release-tailwind-stash-mrwak9dn/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/release-tailwind-stash-mrwak9dn/SKILL.md' && test -s '.skill-downloads/release-tailwind-stash-mrwak9dn/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/release' && cp -R '.skill-downloads/release-tailwind-stash-mrwak9dn' '.claude/skills/release'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/release-tailwind-stash-mrwak9dn'

openskills read 'release-tailwind-stash-mrwak9dn'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/release-tailwind-stash-mrwak9dn/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

Configure a Chat Channel with SecretRefs

DevOps

Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.

Claude CodeCodexintermediateSafe 387,940
Skills Guide Bot

Investigate ClickHouse CI Failures

DevOps

Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.

Claude CodeadvancedSafe 49,516
Skills Guide Bot

Ansible PR Review

DevOps

Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.

Claude CodeintermediateSafe 70,491
Skills Guide Bot