finalize-release

Orchestrate GitHub tag creation, release publishing, and master-to-dev branch synchronization.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual, multi-step process of finalizing a production release, ensuring that GitHub tags, releases, and branch synchronization are handled consistently and safely.

Core Features & Use Cases

  • Unified Release Flow: Orchestrates tag creation, GitHub Release publishing, and dev-branch synchronization in one atomic operation.
  • Safe Branch Management: Automatically manages dev branch rulesets, temporarily relaxing restrictions to allow merge commits for synchronization while ensuring they are restored immediately after.
  • Use Case: After merging a release PR to master, use this skill to instantly tag the version, publish release notes, and sync the changes back to the development branch without manual intervention or risk of history corruption.

Quick Start

Use the finalize-release skill to complete the post-release flow for the current version.

Frequently Asked Questions about finalize-release

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

FAQPage Schema
How do I automate GitHub release publishing and tag creation after merging a release PR?

Automating GitHub release publishing and tag creation requires validating repository state, tagging the version, and publishing release notes. This skill orchestrates these tasks into one atomic operation alongside master-to-dev branch synchronization.

How does branch synchronization work when finalizing a mobile app release?

Branch synchronization during release finalization merges changes from the master branch back to the dev branch. This skill temporarily relaxes dev branch rulesets to allow merge commits, then immediately restores restrictions to ensure history integrity.

Can I use this workflow to sync master to dev without violating branch protection rules?

Syncing master to dev with branch protection rules active requires temporary ruleset modifications. This skill manages those temporary changes automatically, allowing required merge commits before immediately restoring the original branch restrictions.

What is the best way to manage post-release workflows for applications with strict merge commit history?

Managing post-release workflows with strict merge commit history requires atomic execution of tag creation, release publishing, and branch synchronization. This skill validates repository state first to ensure safe, consistent finalization without history corruption.

Does this release automation process handle temporary GitHub ruleset modifications safely?

Handling temporary GitHub ruleset modifications safely involves relaxing restrictions only for necessary merge commits and restoring them immediately after. This skill automates that lifecycle to ensure branch protection rules remain enforced long-term.

Why do I need to validate repository state before publishing a GitHub release?

Validating repository state before publishing a GitHub release ensures the branch is stable and ready for tags. This skill checks repository conditions first to guarantee atomic execution and prevent partial or corrupted release finalizations.