skills.rest
Roxabi
RoxabiOFFICIAL
Explore all skills by this author →
Website𝕏@roxabi_GitHub

promote

Automate staging-to-main branch promotion with pre-flight checks, versioning, and pull request creation.

9|1|Updated Feb 28, 2026
Search Tags:#changelog#versioning#deployment#git workflow#github actions#release
One-click install
npx skills add https://github.com/Roxabi/roxabi-plugins --skill promote-roxabi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: promote
Source: https://github.com/Roxabi/roxabi-plugins/tree/main/plugins/dev-core/skills/promote
Command: npx skills add https://github.com/Roxabi/roxabi-plugins --skill promote-roxabi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the complex process of promoting code from a staging environment to the main branch, ensuring a smooth and reliable release cycle.

Core Features & Use Cases

  • Automated Pre-flight Checks: Verifies CI status, open PRs, and code differences before promotion.
  • Version Bumping & Changelog Generation: Automatically determines the next version and updates release notes.
  • PR Creation & Finalization: Creates promotion PRs and handles post-merge tagging and GitHub Releases.
  • Use Case: A development team needs to deploy a new feature. They run /promote on the staging branch, and the skill handles all the necessary checks, versioning, changelog updates, and creates a PR to merge into main, minimizing manual errors and saving developer time.

Quick Start

Run the promote skill to start the full release process from staging to main.

Frequently Asked Questions about promote

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

FAQPage Schema
How do I automate promoting code from a staging branch to main?▼

Automating staging to main branch promotion involves running pre-flight checks, version bumping, and generating a pull request. This skill orchestrates the entire git workflow, verifying CI status and code differences before merging to ensure a reliable release cycle.

What is the best way to generate changelogs and bump versions during a release?▼

Generating changelogs and bumping versions during a release is handled automatically as part of the promotion process. The skill determines the next version number, updates release notes, and commits the changes before creating a pull request to merge into main.

Can I test a git workflow deployment before finalizing the release?▼

Yes, you can test a deployment using the dry-run option. This allows you to simulate the promotion process, checking CI status and code differences without actually creating a pull request, bumping versions, or finalizing the GitHub release.

How does a staging to main release handle post-merge tagging and GitHub releases?▼

Post-merge tagging and GitHub releases are handled through the finalization step. After the promotion pull request is merged into main, the skill finalizes the release by applying git tags and publishing the corresponding GitHub release.

Do I need to manually check CI status before creating a release pull request?▼

No, manual CI checks are not needed before creating a release pull request. The skill performs automated pre-flight checks that verify CI status, identify open pull requests, and check code differences before initiating the promotion to main.

Related Skills

Explore More Software Engineering Skills→
TMI-appsTMI-apps
2

push

Validate and push committed Git changes to a remote repository.

Official
Intermediate
girijashankarjgirijashankarj
28

release-manager

Automate version bumps, changelog generation, and Git tag releases.

Community
Advanced
GolferGeekGolferGeek

GitHub Workflow

Standardize GitHub branching, pull requests, code reviews, and CI/CD pipelines.

Community
Basic
ScivorScivor

ship

Automate release orchestration by merging changes, running tests, and creating a PR.

Community
Advanced