create-release-pr

Create production release branches and pull requests for mobile apps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, npm.

What problem does it solve?

This skill eliminates the manual, error-prone process of cutting release branches, bumping versions, and verifying code quality before a production deployment.

Core Features & Use Cases

  • Automated Release Workflow: Handles branch creation, version bumping, and quality gate verification in one flow.
  • Safety-First Validation: Ensures code quality via linting, type checking, and testing before any push or PR creation.
  • Use Case: When preparing for a new app version, use this skill to safely branch from dev, update the version, run all quality checks, and open a release PR to master.

Quick Start

Use the create-release-pr skill to initiate the release process for version 10.4.2.

Frequently Asked Questions about create-release-pr

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

FAQPage Schema
How do I automate creating a production release branch and pull request?

To automate creating a production release branch and pull request, you can use an automation skill that handles branch creation, version bumping, and quality gate verification in one flow. This eliminates the manual, error-prone process of cutting release branches.

Do I need gh CLI and npm to automate release branch workflows?

Yes, you need gh CLI, git, and npm to automate release branch workflows. These dependencies are required to perform repository operations, manage dependency updates, and execute the git synchronization workflows necessary for stable releases.

How do I bump the app version and run quality checks before opening a release PR?

To bump the app version and run quality checks before opening a release PR, the automation safely branches from dev, updates the version, and runs linting, type checking, and testing. This safety-first validation ensures code quality before any push or PR creation.

What is the best way to cut a release branch from dev to master safely?

The best way to cut a release branch from dev to master safely is to use an automated release workflow. It branches from dev, bumps the version, verifies code quality via linting and testing, and opens a release PR to master, ensuring stable releases.

Can I use an automated release workflow for mobile application versioning?

Yes, you can use an automated release workflow for mobile application versioning. The process manages version bumping, code quality verification, and git synchronization workflows specifically designed to ensure stable mobile app production deployments.

Why does my release pull request fail code quality verification before a push?

A release pull request fails code quality verification when linting, type checking, or testing detects errors before any push or PR creation. This safety-first validation prevents broken code from reaching the master branch during the release process.