skills.rest
a3tai
a3taiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

release-tag

Create a GitHub release from a Git tag after a PR merge.

35|9|Updated Feb 20, 2026
Search Tags:#git#version control#github#release automation#continuous integration
One-click install
npx skills add https://github.com/a3tai/openclaw-go --skill release-tag-a3tai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-tag
Source: https://github.com/a3tai/openclaw-go/tree/main/.opencode/skills/release-tag
Command: npx skills add https://github.com/a3tai/openclaw-go --skill release-tag-a3tai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of GitHub releases from tags created after a PR merge, reducing manual steps and ensuring consistency.

Core Features & Use Cases

  • Tag Creation: Automatically creates a Git tag after a PR merge to main.
  • Release Creation: Generates a GitHub release with a corresponding tag.
  • Workflow Integration: Follows the repository's tag and release workflow.
  • Use Case: Use this Skill to streamline the release process after a PR is merged, ensuring tags and releases are created automatically and consistently.

Quick Start

Run the skill to create a GitHub release after merging a PR and ensuring all checks are passed.

Frequently Asked Questions about release-tag

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

FAQPage Schema
How do I automate GitHub release creation after a PR merge?▼

Automating GitHub release creation after a PR merge involves automatically generating a Git tag on the main branch and using it to create a corresponding GitHub release, ensuring consistency in continuous integration workflows.

What is the best way to streamline Git tag and release management in continuous integration?▼

Streamlining Git tag and release management in continuous integration is achieved by automating tag creation immediately following a PR merge, which then triggers a consistent GitHub release generation process.

Do I need GitHub CLI and Git to automate release creation from merged PRs?▼

Yes, you need both Git and GitHub CLI to automate release creation from merged PRs. Git handles the semantic versioning and tag creation, while GitHub CLI interacts with the repository to generate the actual release.

How does semantic versioning work with automated Git tag creation?▼

Semantic versioning works with automated Git tag creation by providing a structured versioning scheme that the workflow uses to label tags generated after a PR merge, ensuring clear release progression.

Can I use this release automation workflow for any Git-based repository?▼

Yes, you can use this release automation workflow for any Git-based repository that integrates with GitHub. It is specifically designed for continuous integration environments utilizing Git and GitHub CLI for version control.

Related Skills

Explore More Software Engineering Skills→
thatrebeccaraethatrebeccarae
97

release-notes

Generate Keep a Changelog entries and GitHub releases from git history.

Community
Intermediate
adamfilliadamfilli
11

release

Automate version bumps, commits, and GitHub releases for software projects.

Community
Intermediate
George-RDGeorge-RD
8

release

Automate software releases across GitHub Releases, crates.io, npm, PyPI, and Homebrew registries.

Community
Advanced
figuedmundofiguedmundo

changelog-automation

Automate changelog generation and release management with Conventional Commits.

Community
Advanced