midnite-release-prep

Analyzes commits since the last release and prepares a draft release branch with version bumps and changelog.

Updated Sep 1, 2026
One-click install
npx skills add https://github.com/bilo-io/midnite-studio --skill midnite-release-prep-bilo-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: midnite-release-prep
Source: https://github.com/bilo-io/midnite-studio/tree/main/.agents/skills/midnite-release-prep
Command: npx skills add https://github.com/bilo-io/midnite-studio --skill midnite-release-prep-bilo-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Preparing a software release involves error-prone manual work: deciding the next version number, curating changelog entries from raw commits, and bumping package versions consistently. This Skill automates the reversible half of that flow while enforcing a fixed lockstep versioning policy and stopping before anything irreversible. ## Core Features & Use Cases - Automatic version proposal: Parses conventional commits since the last tag and applies tested bump rules (breaking → major, feat → minor, fix-only → patch) via the shared planRelease logic, including correct first-release handling. - Draft release branch: Creates a release/vX.Y.Z branch with curated Keep-a-Changelog entries and package.json version bumps, committed but never tagged or pushed. - Ephemeral test releases: Plans throwaway test tags on the current tree to validate install.sh from other machines without touching versions or the changelog. - Use Case: After merging a sprint of features into main, invoke the Skill to get a proposed v1.4.0 release branch with a curated changelog draft, review it, then hand off to the completion step for tagging and publishing. ## Quick Start Ask the AI to prepare the next Midnite Studio release by analyzing commits since the last tag and drafting the release branch.

Frequently Asked Questions about midnite-release-prep

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

FAQPage Schema
How do I prepare a release branch from conventional commits?▼

Run the Skill on an up-to-date main branch with a clean working tree. It fetches tags, categorizes commits since the last release with conventional-commit parsing, proposes the bump level, and creates a release/vX.Y.Z branch with version bumps and a curated changelog draft.

How is the next version number decided in a monorepo release?▼

The strongest commit signal wins: any BREAKING CHANGE triggers a major bump for all packages, any feat triggers a lockstep minor bump, and fix-only ranges bump only the changed packages as patches. The shared planRelease function computes all next versions in one call.

What happens on the first release when no tags exist?▼

The first-release case ships the versions already in the tree without bumping. Commits are not consulted for categorization, since the entire history would otherwise misclassify as a minor bump; the tag is built from the current version.

Does this Skill tag or push the release to GitHub?▼

No. It only creates a local draft branch with the changelog and version bumps, stopping before anything irreversible. Tagging, pushing, and creating the GitHub Release are handed off to the separate midnite-release-complete step.

Can I test the install script without a real release?▼

Yes. Choose the ephemeral test release option, which skips version bumps and changelog edits entirely and plans a throwaway test tag on the current tree for validating install.sh from other machines, to be deleted after testing.