skills.rest
supersuit-tech
supersuit-techOFFICIAL
Explore all skills by this author →
GitHub

version-tag

Create and push git tags for mobile, cli, or web packages from the main branch.

4|1|Updated Feb 28, 2026
Search Tags:#git#versioning#semver#release-management#tagging#github-api
One-click install
npx skills add https://github.com/supersuit-tech/permission-slip --skill version-tag
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: version-tag
Source: https://github.com/supersuit-tech/permission-slip/tree/main/.claude/skills/version-tag
Command: npx skills add https://github.com/supersuit-tech/permission-slip --skill version-tag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tagging releases for multiple packages from the main branch can be error-prone and manual; this skill standardizes and automates version tagging and synchronization with package.json.

Core Features & Use Cases

  • Auto-increment patch version when no explicit version is provided.
  • Validate input package is one of mobile, cli, or web; check for existing tags; resolve main SHA; and create remote tags via API.
  • Optional synchronization of package.json version through a PR to ensure tag points to a commit with the correct version.

Quick Start

Run /version-tag cli 0.1.0 to create and push the corresponding tag.

Frequently Asked Questions about version-tag

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate git tag creation for a release from the main branch?▼

You can automate git tag creation by resolving the main branch SHA, verifying existing tags, and pushing the new remote tag via the GitHub API. This process standardizes release tagging safely from the latest main branch.

Can I automatically increment the semver patch version when tagging a release?▼

Yes, you can automatically increment the semver patch version when tagging a release. If you omit the explicit version number during the tagging command, the system applies an automatic patch version increment to generate the next release tag.

How do I synchronize package.json version with a new git tag?▼

To synchronize the package.json version with a new git tag, the workflow optionally creates a pull request to update the file. This ensures the release tag points to a commit containing the correct synchronized package version.

What packages are supported for release tagging and validation?▼

Supported packages for release tagging and validation are specifically mobile, cli, and web. The system validates your input package against this list before proceeding to check existing tags and create the remote release.

Does the version tagging process use the GitHub API to create remote tags?▼

Yes, the version tagging process uses the GitHub API to create remote tags securely. Instead of local git pushes, it resolves the main SHA and submits the tag creation request directly through the API for reliable release management.

What are the limitations when tagging multiple packages from the main branch?▼

A key limitation when tagging packages is that inputs are restricted to the mobile, cli, and web packages. The process also halts if existing tags are detected, preventing duplicate releases on the same main branch commit.

Related Skills

Explore More Software Engineering Skills→
adamfilliadamfilli
11

git-back-to-main

Reset a local Git repository to the latest main branch.

Community
Basic
jubscodesjubscodes
49

gspdev-publish

Bump version numbers, update changelogs, and prepare npm release artifacts.

Community
Advanced
INNERJOINTINNERJOINT

release

Automate version bumps, tests, npm publishing, and GitHub releases.

Community
Advanced
edictum-aiedictum-ai
29

release

Automate semantic version bumping, tagging, pushing, and GitHub Release creation.

Official
Intermediate