release-prep

Generate changelogs, detect breaking API changes, and recommend semantic version bumps for Rust, Python, and JavaScript projects.

2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/jscott3201/ai-agent-skills --skill release-prep-jscott3201
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-prep
Source: https://github.com/jscott3201/ai-agent-skills/tree/main/skills/release-prep
Command: npx skills add https://github.com/jscott3201/ai-agent-skills --skill release-prep-jscott3201

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prepare a crate or project for release with a clear, reviewable process that detects breaking API changes, drafts user-facing changelogs, suggests semantic version bumps, and verifies documentation and packaging before tagging.

Core Features & Use Cases

  • Breaking-change detection: Integrates cargo-semver-checks for Rust and provides manual guidance for Python/JS to identify public API changes.
  • Version bump recommendation: Recommends patch/minor/major bumps based on gathered changes and presents rationale for user approval.
  • Changelog generation & docs verification: Drafts user-facing changelog entries from commits, checks README/API docs, and ensures version consistency.
  • Workspace ordering: Computes multi-crate release order from dependency graphs and provides a safe checklist before tagging.
  • Use Case: Use when preparing a Rust workspace release to detect regressions, produce a migration note for breaking changes, and tag a coordinated multi-crate release.

Quick Start

Run release-prep for the crate or workspace name to generate a suggested version bump and a draft changelog for your review.

Frequently Asked Questions about release-prep

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

FAQPage Schema
How do I generate a changelog and determine the correct semver bump for my Rust crate?

To generate a changelog and determine a semver bump, the release-prep process analyzes your commits and detects breaking API changes to recommend a patch, minor, or major version bump for your Rust crate for user approval.

Can I detect breaking API changes in Python or JavaScript projects before tagging a release?

Yes, you can detect breaking API changes in Python and JavaScript projects using manual guidance provided during the release preparation process, while Rust projects utilize automated cargo-semver-checks integration for thorough public API verification.

What is the best way to coordinate a multi-crate workspace release with correct dependency ordering?

The best way to coordinate a multi-crate workspace release is to compute the release order from the dependency graph, ensuring safe checklist verification and proper dependency ordering before tagging the coordinated release.

Does release-prep verify documentation and version consistency before generating a final changelog?

Yes, release-prep verifies documentation by checking README and API docs, ensures version consistency across the project, and drafts user-facing changelog entries from your recent commits before tagging.

When should I use a dedicated release preparation workflow instead of just tagging a git commit?

You should use a dedicated release preparation workflow when you need to detect regressions, produce migration notes for breaking changes, verify packaging, and safely coordinate multi-crate releases before tagging.