cut

Create a versioned release candidate branch from origin/develop and push it.

Updated Apr 17, 2026

Search Tags:#automation #git #workflow #branching #staging #tagging #release-candidate

Ready to run

npx skills add https://github.com/smallorbit/smallorbit-plugins --skill cut

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cut
Source: https://github.com/smallorbit/smallorbit-plugins/tree/main/plugins/flowkit/skills/cut
Command: npx skills add https://github.com/smallorbit/smallorbit-plugins --skill cut

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a versioned release candidate branch from origin/develop, then automatically stage it if origin/staging exists.

Core Features & Use Cases

Deterministic RC naming based on the current date, with incremental suffix numbers.
Pushes the new RC branch to origin and creates a corresponding tag.
Detects staging availability at runtime and auto-stages when present.
Transparent reporting of RC branch name and staging status.

Quick Start

Create an RC for today on origin/develop and push it, then report the branch name and whether staging exists.

Frequently Asked Questions about cut

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

FAQPage Schema

How do I automate creating a release candidate branch from develop in Git?▼

Automating release candidate branch creation from origin/develop involves fetching the remote state, computing a deterministic RC name like rc/YYYY-MM-DD.N, pushing the branch and tag, and reporting the RC name and staging status.

What is the naming convention for automated Git release candidate branches?▼

Automated Git release candidate branches use a deterministic naming convention of rc/YYYY-MM-DD.N, where the date is the current day and N is an incremental suffix number to distinguish multiple RCs created on the same date.

How does automatic staging work when creating a release candidate branch?▼

Automatic staging works by detecting the presence of an origin/staging branch at runtime, conditionally staging the newly created release candidate branch if staging exists, and transparently reporting the staging status upon completion.

Can I auto-stage a release candidate if an origin/staging branch exists?▼

Yes, you can auto-stage a release candidate if origin/staging exists, as the workflow detects staging availability at runtime and conditionally pushes and stages the new RC branch from origin/develop when the staging branch is present.

What is the best way to tag and push a versioned release candidate branch?▼

The best way to tag and push a versioned release candidate branch is using standard Git tooling and Bash to fetch remote state, compute the rc/YYYY-MM-DD.N name, push the new branch and corresponding tag to origin, and report the RC name.

Why does my release candidate workflow require fetching remote state in Git?▼

Fetching remote state in Git is required for release candidate workflows to accurately compute the incremental suffix for the rc/YYYY-MM-DD.N naming convention and to detect whether origin/staging exists for conditional auto-staging.