release-tagging

Name: release-tagging
Availability: InStock
Author: tubtrb

Automate release tagging, merged-branch cleanup, and codex/next synchronization from main.

Updated Mar 15, 2026

Search Tags:#git #workflow #release-management #tagging #version-control #branch-cleanup #release-tagging

Ready to run

npx skills add https://github.com/tubtrb/autoreport --skill release-tagging

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-tagging
Source: https://github.com/tubtrb/autoreport/tree/main/codex/skills/release-tagging
Command: npx skills add https://github.com/tubtrb/autoreport --skill release-tagging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and maintain a clean, auditable release history by automating release backup tagging, post-merge branch cleanup, and synchronization of codex/next from main after a release.

Core Features & Use Cases

Automated creation and verification of annotated release tags on main (v<version>) with safeguards against overwriting existing tags.
Post-merge branch cleanup and codex/next refresh to keep release history consistent and ready for the next development cycle.
Clear operational guidance for release engineers to run deterministic, repeatable release workflows.

Quick Start

Tag a new release by creating an annotated v<version> tag on main, clean up the merged source branches, and refresh codex/next from main.

Frequently Asked Questions about release-tagging

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

FAQPage Schema

How do I automate git release tagging and branch cleanup after merging?▼

Automate git release tagging and branch cleanup by creating annotated v<version> tags on main, guarding against overwriting existing tags, cleaning merged source branches, and refreshing codex/next to keep release history consistent.

What is the safest way to create annotated release tags on main without overwriting history?▼

The safest way to create annotated release tags on main is to specify tag targets and apply safeguards against overwriting existing tags, requiring explicit pushes to preserve deterministic release history.

How do I sync codex/next from main after a git release?▼

Sync codex/next from main after a git release by refreshing the branch directly from main, ensuring the repository is ready for the next development cycle while keeping release-candidate history consistent.

Can I use this release workflow for post-merge branch cleanup and version control?▼

Yes, you can use this release workflow for post-merge branch cleanup and version control as it automates repository-local release tagging and codex/next synchronization without requiring external dependencies.

Why do I need explicit pushes when tagging releases in git?▼

You need explicit pushes when tagging releases in git to prevent accidental overwrites and ensure deterministic, auditable release history is maintained safely before changes are finalized remotely.

When should I not use automated release tagging for version control?▼

You should not use automated release tagging when your version control workflow does not follow a main-to-codex/next synchronization model or lacks distinct post-merge branch cleanup requirements.