skills.rest
smallorbit
smallorbitCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

release

Create and merge release PRs, tag commits, close issues, and clean RC branches.

Updated Apr 17, 2026
Search Tags:#automation#git#workflow#devops#github#release#pr
One-click install
npx skills add https://github.com/smallorbit/smallorbit-plugins --skill release-smallorbit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/smallorbit/smallorbit-plugins/tree/main/plugins/flowkit/skills/release
Command: npx skills add https://github.com/smallorbit/smallorbit-plugins --skill release-smallorbit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates end-to-end release governance by orchestrating PR creation from a release candidate, merging into main, tagging the release, closing referenced issues, and cleaning RC branches to keep branches tidy.

Core Features & Use Cases

  • Open a PR from the release source to main and merge it to promote a release
  • Tag the commit, collect and close linked issues, and delete stale RC branches
  • Synchronize develop after release and provide a repeatable rollback-safe workflow

Quick Start

Promoting the current RC to production by creating a release PR from the source branch to main and tagging the commit.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate a GitHub release workflow from PR merge to tagging?▼

Automating a GitHub release workflow involves creating a PR from a release source into main, merging it, tagging the commit, closing referenced issues, and cleaning RC branches. This Skill orchestrates that entire end-to-end release governance process automatically.

What is the best way to manage staging, RC branches, and development synchronization in Git?▼

Managing staging, RC branches, and development synchronization is handled by promoting release candidates into main via PRs, tagging commits, and synchronizing develop after release. This approach provides a repeatable rollback-safe workflow for GitHub.

Do I need GitHub CLI and Bash tooling to automate release PRs and tags?▼

Yes, automating release PRs and tags requires Bash tooling and the GitHub CLI. The workflow validates branch existence, ensures release notes are included when present, and relies on these tools to execute the end-to-end release governance commands.

Can I automatically close referenced issues and delete stale RC branches after merging a release PR?▼

Yes, you can automatically close referenced issues and delete stale RC branches after merging a release PR. The workflow tags the merged commit, collects linked issues, closes them, and cleans RC branches to keep the repository tidy.

How does this release automation handle release notes and branch validation?▼

Release automation handles release notes by ensuring they are included when present during the PR creation into main. It also validates branch existence before proceeding, preventing invalid release sources from being merged or tagged.

Related Skills

Explore More Software Engineering Skills→
typemdtypemd
9

create-release

Gather closed issues and commits to draft release notes and create a GitHub draft release.

Official
Advanced
messebmesseb

cicd

Manage GitHub release pipelines from develop branches to production tags.

Community
Advanced
rsyslogrsyslog
2.3k

rsyslog_continuous_issue_session

Orchestrate long-running rsyslog issue-resolution sessions with work unit management and PR babysitting.

Official
Advanced
joelreymontjoelreymont
43

Release Skill

Tag the current commit and push releases to GitHub for CI builds.

Community
Advanced