skills.rest
storj
storjOFFICIAL
Explore all skills by this author →
Website𝕏@storjGitHub

point-release

Creates Storj point releases by cherry-picking commits onto release branches and tagging versions.

3.3k|427|Updated Apr 4, 2018
Search Tags:#Git#cherry-pick#tagging#storj#gitHub cli#release branch#point release
One-click install
npx skills add https://github.com/storj/storj --skill point-release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: point-release
Source: https://github.com/storj/storj/tree/main/.claude/skills/point-release
Command: npx skills add https://github.com/storj/storj --skill point-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Landing a fix on a Storj release branch after it has been cut requires a careful sequence of cherry-picks, pull requests, and version tags; this Skill guides that process without skipping review or tagging steps.

Core Features & Use Cases

  • Cherry-pick workflow: Fetches the release branch, cherry-picks one or more commits from main, and surfaces merge conflicts to the user instead of guessing resolutions.
  • PR and tagging automation: Opens a pull request targeting the release branch with gh, then creates the point release tag via scripts/tag-release.sh after the PR merges.
  • Guardrails: Requires explicit user confirmation before any push to origin and enforces that tag versions match the release branch (e.g. release-v1.38 maps to v1.38.x).
  • Use Case: A fix merged to main must ship as v1.38.1; the Skill cherry-picks the commit onto release-v1.38, opens the PR, and tags v1.38.1 once merged.

Quick Start

Create a point release v1.38.1 by cherry-picking commit abc1234 onto the release-v1.38 branch.

Frequently Asked Questions about point-release

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

FAQPage Schema
How do I create a point release for a Storj release branch?▼

Fetch tags, check out the release branch, cherry-pick the fix commits, push a point_release branch, and open a PR against the release branch. After the PR merges, run scripts/tag-release.sh with the new patch version and push the tag.

How do I cherry-pick a commit onto a release branch in git?▼

Check out the release branch and pull the latest remote state, then run git cherry-pick with the commit hash. For multiple commits, list them oldest first so they apply in the correct order.

What happens if a cherry-pick has merge conflicts?▼

The Skill stops and surfaces the conflicting files via git status rather than resolving them automatically. The user resolves the conflicts, then continues with git cherry-pick --continue or aborts with git cherry-pick --abort.

Can I push the cherry-pick directly to the release branch?▼

No. The cherry-pick goes on a separate branch such as point_release_v1.38.1, and a pull request is opened against the release branch. The tag is created only after that PR is reviewed and merged.

Why use scripts/tag-release.sh instead of git tag?▼

The tag-release.sh script sets release-mode defaults and verifies a clean working tree before tagging. It requires a version matching vMAJOR.MINOR.PATCH that corresponds to the target release branch.

Related Skills

Explore More Software Engineering Skills→
sahil-vasanisahil-vasani

create-backport-branch

Create an ai-backport branch and cherry-pick GitHub PR commits onto a target release branch.

Community
Advanced
dropseeddropseed
1.0k

plainx-release

Bump versions, generate changelogs, and tag Git releases for Python packages.

Official
Advanced
dmzoneilldmzoneill
2

hotfix

Cherry-pick a commit from a development branch to a release branch.

Community
Intermediate
c15tc15t
1.8k

vercel-react-best-practices

Apply React and Next.js best practices for code splitting and performance optimizations.

Official
Advanced