skills.rest
Jem-Open
Jem-OpenOFFICIAL
Explore all skills by this author →
GitHub

gtm

Automate GitHub releases, version bumps, branching, and PR workflows.

3|1|Updated Mar 9, 2026
Search Tags:#automation#git#versioning#github#release#pull-request
One-click install
npx skills add https://github.com/Jem-Open/jem-agent-skills --skill gtm-jem-open
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gtm
Source: https://github.com/Jem-Open/jem-agent-skills/tree/main/skills/gtm
Command: npx skills add https://github.com/Jem-Open/jem-agent-skills --skill gtm-jem-open

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the Go-to-market release process by bumping the version, creating a release branch, publishing a GitHub release with auto-generated notes, and opening PRs into the base branch and main, with auto-merge by default when checks pass.

Core Features & Use Cases

  • Bump the project version from the version file and create a release branch.
  • Publish a GitHub release with auto-generated notes and open PRs into the base branch and main.
  • Automatically merge PRs by default once required checks and reviews pass, with an option to disable auto-merge.
  • Provide a consolidated summary and switch back to the base branch after the release.

Quick Start

Trigger the release workflow by running /gtm with one of --patch, --minor, or --major on your development branch.

Frequently Asked Questions about gtm

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

FAQPage Schema
How do I automate GitHub release workflows and PR generation?▼

To automate GitHub release workflows, you can trigger an automated process that bumps project versions, creates release branches, publishes GitHub releases with auto-generated notes, and opens pull requests into base and main branches.

How do I automatically merge release pull requests once checks pass?▼

You can automatically merge release pull requests by enabling auto-merge by default, which merges PRs into the base branch and main once required checks and reviews pass. This functionality can be optionally disabled.

Do I need the GitHub CLI to automate version management and tagging?▼

Yes, automating version management and tagging requires validating the GitHub CLI. The deterministic release process reads a version file, validates the GitHub CLI, creates a release, and opens PRs.

What is the best way to bump project versions for a new release?▼

The best way to bump project versions is by running a release command with --patch, --minor, or --major on your development branch to automatically create a release branch and update the version file.

Can I disable auto-merge for release pull requests into the main branch?▼

Yes, you can disable auto-merge for release pull requests. While auto-merge is enabled by default to merge PRs once checks pass, an option is provided to turn it off during the release workflow.

Related Skills

Explore More Software Engineering Skills→
Zidane786Zidane786

release

Coordinate version checks, file updates, and PR creation for Kimi Code CLI releases.

Community
Advanced
mvillmowmvillmow
18

gh-implement-issue

Automate GitHub issue implementation from branch creation to pull request.

Community
Intermediate
arcasilesgrouparcasilesgroup
54

ai-pr

Automate governed pull request workflows with pre-push gates and squash merge.

Official
Advanced
hiddink-aihiddink-ai
1

hiddink-harness:npm-version

Automate npm package version bumps, changelogs, and git tags.

Official
Intermediate