release

Generate release notes, changelog entries, and migration guides from git history.

24|3|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/Borda/.home --skill release-borda
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/Borda/.home/tree/main/.claude/skills/release
Command: npx skills add https://github.com/Borda/.home --skill release-borda

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complex and time-consuming process of preparing and communicating software releases, ensuring consistency and reducing manual errors.

Core Features & Use Cases

  • Automated Release Notes: Generates user-facing release notes based on commit history and PRs.
  • Changelog Management: Prepends new release entries to your CHANGELOG.md file.
  • Release Auditing: Checks for pre-release readiness, including blockers, documentation alignment, and version consistency.
  • Migration Guides: Creates guides for breaking changes between versions.
  • Use Case: When you're ready to ship a new version, use this Skill to automatically draft the public release notes, update the changelog, and perform a final readiness check, all with a single command.

Quick Start

Use the release skill to prepare version 1.3.0 of the project.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate release notes generation from git commit history?

Automating release notes generation involves analyzing git commit history and pull request data to draft public notes and internal summaries. This process extracts commit messages and PR titles to structure audience-specific release documentation automatically.

What is the best way to automate changelog management for new versions?

Automated changelog management prepends newly generated release entries directly to your CHANGELOG.md file. By parsing git history, it ensures chronological consistency and aggregates changes without manual text entry.

Can I perform a pre-release readiness audit using GitHub CLI and git commands?

Yes, pre-release readiness audits can be automated using GitHub CLI and git commands. This checks for release blockers, documentation alignment, and version consistency before publishing a new release.

How do I generate migration guides for breaking changes between versions?

Generating migration guides for breaking changes requires analyzing git history for significant modifications between versions. The system identifies breaking changes and structures them into a guide for users upgrading.

Does automated release creation work without external dependencies?

Yes, this automated release creation works without external dependencies. It leverages existing GitHub CLI and local git commands to track changes, perform readiness checks, and create releases directly.