agentsclimarketplace
Sign in

Release tag

Skill kodingwarrior/minimalism-workflow/skills/release-tag

Create a git tag from the project's version file (package.json, Cargo.toml, pubspec.yaml, build.gradle, etc.). This skill should be used when the user wants to tag a release, create a version tag, or tag the current commit for release.From its SKILL.md

Install
npx -y skills add kodingwarrior/minimalism-workflow --skill release-tag

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.9 KB, as published. Nobody here has run it

Release Tag

Create an annotated git tag based on the project's version file.

Arguments: <message> (optional — annotation message for the tag)

Instructions

Phase 1: Read Version

Detect the project type by checking for version files in this order. Use the first match found.

Node.js — package.json

  1. Read package.json and extract the version field.
  2. Tag: v{version} (e.g., v0.3.0).

Rust — Cargo.toml

  1. Read Cargo.toml and extract version from [package].
  2. Tag: v{version}.

Flutter / Dart — pubspec.yaml

  1. Read pubspec.yaml and extract the version field (e.g., 1.2.0+3).
  2. Use only the semver part before + for the tag: v{semver}.

Android — app/build.gradle.kts or app/build.gradle

  1. Extract the versionName value (e.g., versionName = "1.2.0").
  2. Tag: v{versionName}.
  3. If the argument indicates a version bump (e.g., the tag doesn't match the current versionName), also increment versionCode by 1 and update versionName to the target version, then commit the change before tagging.

Python — pyproject.toml

  1. Read pyproject.toml and extract version from [project] or [tool.poetry].
  2. Tag: v{version}.

Go — version.go or git tags

  1. Look for a Version constant in common locations (version.go, cmd/version.go, internal/version/version.go).
  2. If not found, fall back to the latest v* git tag and suggest the next patch bump.
  3. Tag: v{version}.

Elixir — mix.exs

  1. Read mix.exs and extract the version field from the project/0 function.
  2. Tag: v{version}.

Fallback

If none of the above files are found, ask the user for the version string.

Phase 2: Validate

  1. Check if the tag already exists:

    git tag --list 'v{version}'

    If it exists, inform the user and halt. Suggest bumping the version first.

  2. Check for uncommitted changes:

    git status --porcelain

    If there are uncommitted changes, warn the user and ask whether to proceed.

  3. Show the user what will be tagged:

    git log -1 --oneline

Phase 3: Confirm

Present the tag details and ask the user to confirm:

  • Tag: v{version}
  • Commit: {short hash} {message}
  • Message: The annotation message (argument or auto-generated)

If no <message> argument was provided, use:

Release v{version}

Phase 4: Create Tag

Create an annotated tag:

git tag -a v{version} -m "{message}"

Phase 5: Push (Optional)

Ask the user if they want to push the tag:

git push origin v{version}

Only push if the user confirms. Display the result.

Keep looking

Skills are one crate of 626,194. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.