prepare-core-kit-release

Bumps Twoliter.toml version and generates changelog from git history for bottlerocket-core-kit releases.

5|12|Updated Nov 24, 2025
One-click install
npx skills add https://github.com/cbgbt/bottlerocket-forest --skill prepare-core-kit-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prepare-core-kit-release
Source: https://github.com/cbgbt/bottlerocket-forest/tree/main/skills/prepare-core-kit-release
Command: npx skills add https://github.com/cbgbt/bottlerocket-forest --skill prepare-core-kit-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the bottlerocket-core-kit release workflow by bumping the release version and updating the changelog to reflect recent changes.

Core Features & Use Cases

  • Bump the release version in Twoliter.toml to a new vX.Y.Z.
  • Generate changelog entries from git history and prepare release notes.
  • Create properly formatted, signed commits for the version bump and changelog update.

Quick Start

In a grove with bottlerocket-core-kit checked out, perform:

  • Update Twoliter.toml to set release-version = "X.Y.Z"
  • git add Twoliter.toml && git commit -s -S -m "twoliter: bump kit version to vX.Y.Z"
  • Update CHANGELOG.md with the new version's changes
  • git add CHANGELOG.md && git commit -s -S -m "changelog: update for vX.Y.Z"

Frequently Asked Questions about prepare-core-kit-release

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

FAQPage Schema
How do I automate a bottlerocket-core-kit release and version bump?

You can automate bottlerocket-core-kit release prep by bumping the release version in Twoliter.toml and generating changelog entries from git history. It creates two signed commits for the version bump and changelog update.

How to generate a changelog from git history for bottlerocket-core-kit?

Generating a changelog from git history for bottlerocket-core-kit involves inspecting merge commits to verify included changes. This Skill formats those changes into CHANGELOG.md updates and commits them using a properly formatted, signed commit.

Does bottlerocket-core-kit require signed commits for version bumps?

Yes, bottlerocket-core-kit release preparation requires signed commits. The workflow enforces commit signing with the -s and -S git flags for both the Twoliter.toml version bump and the CHANGELOG.md update.

What is the correct commit sequence for a bottlerocket-core-kit release?

The correct commit sequence for a bottlerocket-core-kit release is a two-commit process. The first commit bumps the Twoliter.toml version, and the second commit updates the CHANGELOG.md, ensuring the version bump precedes the changelog update.

Can I use this release automation outside a local bottlerocket grove?

No, this release automation specifically applies when preparing a new bottlerocket-core-kit release in a local grove. It requires the bottlerocket-core-kit repository to be checked out to function correctly.