push-tag

Push a version tag to a repository and optionally create a GitHub release.

307|59|Updated Jun 2, 2024
One-click install
npx skills add https://github.com/spiriMirror/libuipc --skill push-tag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: push-tag
Source: https://github.com/spiriMirror/libuipc/tree/main/.cursor/skills/push-tag
Command: npx skills add https://github.com/spiriMirror/libuipc --skill push-tag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Push a version tag and optionally publish a GitHub release directly from your workflow, streamlining release management and reducing manual steps.

Core Features & Use Cases

  • Tag creation on the main branch with validation of existing tags
  • Pushing the new tag to the remote and creating a GitHub release when requested
  • Optional generation of structured release notes to accompany the release

Quick Start

Ask your automation agent to push a new tag for the repository and optionally create a GitHub release.

Frequently Asked Questions about push-tag

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

FAQPage Schema
How do I push a git tag and create a GitHub release from the main branch?

To push a git tag and create a GitHub release, this Skill validates you are on the main branch, creates a version tag, pushes it to the remote repository, and optionally generates a GitHub release with structured release notes via GitHub CLI.

What is the best way to automate versioning and tag creation for CI/CD release management?

Automating versioning and tag creation for release management is handled by this Skill through automatic or provided tag versioning, enforcing branch verification on main before pushing tags to streamline continuous integration workflows.

Can I generate release notes automatically when publishing a GitHub release?

Yes, you can generate structured release notes guidance when publishing a GitHub release, as this Skill optionally creates releases accompanied by release notes via the GitHub CLI to document your version tag pushes.

Does this tagging automation require a specific git branch to push a version tag?

Yes, this tagging automation implements branch verification on the main branch, requiring you to be on main before it will create and push a version tag to ensure consistent release management across repositories.

What happens if I try to create a version tag that already exists in the repository?

When creating a version tag, this Skill performs validation of existing tags in your repository before proceeding, preventing duplicate version tags from being created and pushed to the remote.