publish-release

Create git tags and GitHub Releases for the TrainLCD MobileApp repository.

71|2|Updated Oct 26, 2019
One-click install
npx skills add https://github.com/TrainLCD/MobileApp --skill publish-release-trainlcd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish-release
Source: https://github.com/TrainLCD/MobileApp/tree/main/.claude/skills/publish-release
Command: npx skills add https://github.com/TrainLCD/MobileApp --skill publish-release-trainlcd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the post-merge release process by automating the creation of git tags and GitHub Releases, ensuring consistency and reducing manual overhead after a release PR is merged.

Core Features & Use Cases

  • Automated Tagging: Creates annotated git tags on the master branch head based on semantic versioning.
  • GitHub Release Generation: Automatically publishes a GitHub Release using auto-generated notes based on the diff from the previous tag.
  • Use Case: After merging a release PR for version 10.4.2, use this skill to instantly tag the repository and publish the official release notes to GitHub.

Quick Start

Use the publish-release skill to tag and publish version 10.4.2 for the repository.

Frequently Asked Questions about publish-release

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

FAQPage Schema
How do I automate GitHub releases and git tagging after merging a release PR?

Automating GitHub releases requires targeting the master branch to create annotated git tags and publish release notes. This skill finalizes versioning by generating auto-notes based on the diff from the previous tag after a release PR is merged.

How does automated GitHub release generation work with semantic versioning?

Automated GitHub release generation works by creating annotated git tags on the master branch head using semantic versioning. It then publishes the official release notes to GitHub by calculating the diff from the previous tag.

Do I need the GitHub CLI to automate git tags and repository releases?

Yes, you need the GitHub CLI and git installed to automate repository releases. These dependencies perform authenticated repository operations required to create annotated tags and publish release notes to GitHub.

Can I use this to generate GitHub release notes automatically from a merged PR?

Yes, you can generate GitHub release notes automatically after merging a PR. The skill targets the master branch to create version tags and publishes a GitHub Release using auto-generated notes based on the diff from the previous tag.

What is the best way to streamline post-merge release versioning on GitHub?

The best way to streamline post-merge release versioning is automating the creation of annotated git tags and GitHub Releases. This ensures consistency and reduces manual overhead by instantly tagging the repository and publishing official release notes.