skills.rest
intrusive-memory
intrusive-memoryOFFICIAL
Explore all skills by this author →
WebsiteGitHub

release

Merge pull requests, create annotated Git tags, and generate GitHub releases.

Updated Jan 29, 2026
Search Tags:#automation#git#versioning#github#release#tagging
One-click install
npx skills add https://github.com/intrusive-memory/package-collection --skill release-intrusive-memory
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/intrusive-memory/package-collection/tree/main/skills/release
Command: npx skills add https://github.com/intrusive-memory/package-collection --skill release-intrusive-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of releasing new versions of software by automating the tagging of commits, creation of GitHub releases, and synchronization of development branches.

Core Features & Use Cases

  • Automated Tagging: Creates annotated Git tags for merged Pull Requests.
  • GitHub Release Creation: Generates GitHub releases with titles and notes.
  • Branch Synchronization: Rebases the development branch onto main after a release.
  • Use Case: After a feature is merged into the main branch, use this Skill to tag the release, create a corresponding GitHub release, and ensure the development branch reflects the latest changes.

Quick Start

Release the latest merged PR by tagging and creating a GitHub release.

Frequently Asked Questions about 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 pull request?▼

Automate GitHub releases by merging pull requests, creating annotated Git tags, and generating GitHub releases with titles and notes. This streamlines the release process by automatically tagging commits and synchronizing branches after a feature merge.

What is the best way to sync my development branch with main after a GitHub release?▼

Sync your development branch by rebasing it onto the main branch after a release. This branch synchronization ensures the development branch reflects the latest changes and stays aligned with the newly created Git tags.

Can I create annotated Git tags for merged pull requests using GitHub CLI?▼

Yes, you can create annotated Git tags for merged pull requests using GitHub CLI and Git. This supports version control and release management by automatically tagging commits and generating corresponding GitHub releases.

Does this release automation workflow require manual branch synchronization?▼

No, manual branch synchronization is not required. The workflow manages branch synchronization automatically by rebasing the development branch onto the main branch after completing the GitHub release and tagging process.

Why do I need to rebase the development branch onto main after creating a GitHub release?▼

Rebasing the development branch onto main is needed to ensure branch synchronization after a release. It guarantees the development environment reflects the latest annotated Git tags and merged pull requests from the main branch.

Related Skills

Explore More Software Engineering Skills→
lxh755818-botlxh755818-bot

github-auth

Automates GitHub authentication setup via HTTPS tokens, SSH keys, and gh CLI login.

Community
Intermediate
191854169191854169

openclaw-release-maintainer

Automate and validate OpenClaw release workflows for versioning, changelogs, and publishing.

Community
Advanced
the-agency-aithe-agency-ai
39

Post-Merge

Verify merged pull requests, merge origin updates, and create GitHub releases.

Official
Advanced
bildzeitungbildzeitung
1

release

Propose, confirm, and execute software releases with SemVer and GitHub tagging.

Community
Advanced