Automated summary
Creates an annotated git tag named from the version declared in package.json, after checking for conflicts and getting user confirmation.
Strengths
- Derives the tag name (v{version}) automatically from the package.json version field, keeping the tag consistent with the manifest
- Checks that the tag does not already exist and warns about uncommitted changes before doing anything
- Shows the target commit and asks for confirmation before tagging, then optionally offers to push the tag to origin
Limitations
- Assumes a Node project with package.json and a fixed "v" prefix convention that cannot be configured
- Does not bump the version, generate a changelog, or create more than one tag at a time
- Pushing stays manual and confirmation-gated, so it is not suited to a fully automated release pipeline
Use it when a maintainer wants to tag the current commit for a release using the version already set in package.json.
Avoid it for projects without a package.json, for changing the version number, or for automating a multi-step publishing pipeline.
Security analysis
SafeThe skill only performs read-only git inspections (tag --list, status --porcelain, log) and creates an annotated tag from package.json's version, with push gated behind explicit user confirmation. No destructive, exfiltration, obfuscation, or safety-disabling behavior is present. Commands are transparent and scoped to standard release tagging.
No concerns found
How this analysis is madeExamples
Create the release tag from the version in package.json and show me which commit it points to before you do it.Tag this release as v-current with the annotation message "Release candidate 1".Tag the current commit using the package.json version, then ask me whether to push the tag to origin.name: release-tag description: Create a git tag from the version in package.json. This skill should be used when the user wants to tag a release, create a version tag, or tag the current commit for release.
Release Tag
Create an annotated git tag based on the version in package.json.
Arguments: <message> (optional — annotation message for the tag)
Instructions
Phase 1: Read Version
- Read
package.jsonand extract theversionfield. - Construct the tag name as
v{version}(e.g.,v0.3.0).
Phase 2: Validate
-
Check if the tag already exists:
git tag --list 'v{version}'If it exists, inform the user and halt. Suggest bumping the version first.
-
Check for uncommitted changes:
git status --porcelainIf there are uncommitted changes, warn the user and ask whether to proceed.
-
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.
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 filesThis 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.mdFrom the root of a test project, save the file as .skill-downloads/release-tag-ms47vpqm/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-tag-ms47vpqm' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/release-tag-ms47vpqm/download' --output '.skill-downloads/release-tag-ms47vpqm/SKILL.md.part' && mv '.skill-downloads/release-tag-ms47vpqm/SKILL.md.part' '.skill-downloads/release-tag-ms47vpqm/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-tag-ms47vpqm/SKILL.md' && test -s '.skill-downloads/release-tag-ms47vpqm/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/release-tag' && cp -R '.skill-downloads/release-tag-ms47vpqm' '.claude/skills/release-tag'Cursor
test -f '.skill-downloads/release-tag-ms47vpqm/SKILL.md' && test -s '.skill-downloads/release-tag-ms47vpqm/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/release-tag' && cp -R '.skill-downloads/release-tag-ms47vpqm' '.cursor/skills/release-tag'Codex
test -f '.skill-downloads/release-tag-ms47vpqm/SKILL.md' && test -s '.skill-downloads/release-tag-ms47vpqm/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/release-tag' && cp -R '.skill-downloads/release-tag-ms47vpqm' '.agents/skills/release-tag'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 installationopenskills install './.skill-downloads/release-tag-ms47vpqm'openskills read 'release-tag-ms47vpqm'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 syncManual 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-tag-ms47vpqm/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.
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.
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.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.