skills.rest
DataDog
DataDogOFFICIAL
Explore all skills by this author →
Website𝕏@datadoghqGitHub

release

Identify cherry-pick candidates from main and draft a v2.x release proposal.

8|4|Updated Jul 29, 2022
Search Tags:#git#versioning#release-management#cherry-pick#pr-automation#branch-diff
One-click install
npx skills add https://github.com/DataDog/pprof-format --skill release-datadog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/DataDog/pprof-format/tree/main/.claude/skills/release
Command: npx skills add https://github.com/DataDog/pprof-format --skill release-datadog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a structured release proposal for the v2.x branch by cherry-picking commits from main, ensuring changes are isolated and ready for review.

Core Features & Use Cases

  • Identify commits on main not yet applied to v2.x using branch-diff and present them for confirmation.
  • Determine the next version from PR labels and the tip of v2.x, then draft a coherent release narrative.
  • Create a worktree, perform ordered cherry-picks, and resolve conflicts with user guidance.
  • Generate a final PR against v2.x with a categorized changelog ready for review.

Quick Start

Submit a v2.x release proposal by cherry-picking the approved commits from main and creating a PR against v2.x

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate cherry-picking commits from main to prepare a release branch?▼

To automate cherry-picking for a release, this Skill identifies candidate commits from main using branch-diff, orchestrates a worktree-based workflow to perform ordered cherry-picks, and generates a PR targeting your release branch.

How is the next release version determined when cherry-picking commits?▼

The next version is determined by analyzing PR labels and comparing them against the current release branch tip, ensuring the proposed version increment accurately reflects the included cherry-picked changes.

What's the best way to generate a release proposal with a categorized changelog?▼

You can generate a release proposal by identifying unapplied commits via branch-diff, cherry-picking them into an isolated worktree, and automatically drafting a coherent release narrative with a categorized changelog in the final PR.

How are conflicts handled during automated cherry-pick workflows?▼

During the cherry-pick workflow, the Skill uses an isolated worktree and pauses to resolve any merge conflicts with user guidance before continuing and publishing the final release PR.

Can I use branch-diff to identify which commits are missing from my v2.x branch?▼

Yes, branch-diff is used to automatically identify commits on main that have not yet been applied to the v2.x branch, presenting them for confirmation before initiating the cherry-pick workflow.

When do I need a worktree for cherry-picking release commits?▼

A worktree is needed when orchestrating a release proposal to isolate the cherry-pick process, allowing ordered application of commits and conflict resolution without affecting your current working directory.

Related Skills

Explore More Software Engineering Skills→
ceshineceshine
1

git-workflow

Generate standardized PR descriptions from git state and commit history.

Community
Advanced
annealing-inversionannealing-inversion

sglang-cherrypick

Automate batch cherry-picking of merged PRs onto a release branch via GitHub Actions.

Community
Advanced
nullmastermindnullmastermind
9

spx-git

Automate Git workflows with conventional commits and changelog generation.

Community
Advanced
typemdtypemd
9

create-release

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

Official
Advanced