release-preview

Preview version bumps, changelog updates, and release notes without modifying the repository.

29|5|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/Iron-Ham/claudio --skill release-preview
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-preview
Source: https://github.com/Iron-Ham/claudio/tree/main/.claude/skills/release-preview
Command: npx skills add https://github.com/Iron-Ham/claudio --skill release-preview

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill allows you to preview the exact changes and release notes that would be generated for a new software version without actually making any commits, tags, or releases.

Core Features & Use Cases

  • Dry Run Release: Simulate the entire release process, from version determination to release note generation.
  • Readiness Check: Verify branch status, working directory cleanliness, and GitHub CLI authentication.
  • Change Analysis: Summarize unreleased changes from CHANGELOG.md and categorize them.
  • Version Calculation: Automatically determine the next version based on changes or user input.
  • Release Note Generation: Preview the full release notes as they would appear.
  • Changelog Preview: Show the exact modifications to CHANGELOG.md.
  • Use Case: Before cutting a release, use this skill to ensure the changelog is accurate, the version number is correct, and all release prerequisites are met, preventing accidental premature releases.

Quick Start

Run a dry run of the release process for a minor version update.

Frequently Asked Questions about release-preview

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

FAQPage Schema
How do I preview a git release without making changes to the repository?

To preview a git release without making changes, you can run a dry run simulation. This analyzes unreleased changes, calculates version bumps, and generates changelog and release note previews without creating commits or tags.

Can I check release readiness for my GitHub repository before cutting a version?

Yes, you can check release readiness by verifying branch status, working directory cleanliness, and GitHub CLI authentication. This ensures all release prerequisites are met before committing to the actual version release.

How do I automatically determine the next version number from unreleased changes?

You can automatically determine the next version number by analyzing unreleased changes from your changelog. The simulation categorizes commits and calculates the appropriate semantic version bump for the release preview.

What is the best way to simulate changelog updates for a new software version?

The best way to simulate changelog updates is to use a dry run release process. It summarizes unreleased changes and shows the exact modifications that would be applied to your CHANGELOG.md file without writing to disk.

How does a dry run release generate release notes from git history?

A dry run release generates notes by analyzing unreleased changes in the repository. It categorizes these changes and produces a comprehensive preview of the release notes exactly as they would appear on GitHub.

Do I need GitHub CLI authentication to preview release notes?

Yes, GitHub CLI authentication is verified during the release readiness check. Ensuring proper authentication beforehand allows the release preview to accurately simulate the full release process.