skills.rest
dyoshikawa
dyoshikawaCOMMUNITY
Explore all skills by this author →
GitHub

release-dry-run

Summarize commits and file changes since the latest release tag.

1.3k|142|Updated Jun 18, 2025
Search Tags:#git#changelog#release#semver#dry-run#version-bump
One-click install
npx skills add https://github.com/dyoshikawa/rulesync --skill release-dry-run
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-dry-run
Source: https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/release-dry-run
Command: npx skills add https://github.com/dyoshikawa/rulesync --skill release-dry-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a safe, offline dry run of a release by summarizing changes since the last release and suggesting the appropriate semantic version bump.

Core Features & Use Cases

  • Changelog-style summary: Generates a concise list of commits and file changes since the latest tag.
  • Version bump guidance: Recommends MAJOR, MINOR, or PATCH based on the changes.
  • Release-notes ready output: Produces a structured summary suitable for release notes and planning.
  • Use Case: When preparing a release, run this to know what changed and how to bump the version before opening a release PR.

Quick Start

Run rulesync release-dry-run to generate a changes report and version bump recommendation for the next release.

Frequently Asked Questions about release-dry-run

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

FAQPage Schema
How do I preview version bumps and changes before opening a release PR?▼

Preview release impact by scanning commit history and file diffs between the latest git tag and HEAD to generate a changelog summary and recommend the appropriate semantic version bump.

What is the best way to determine if a release requires a MAJOR, MINOR, or PATCH version bump?▼

Determine the semantic version bump by analyzing commit messages and file changes since the last release tag, providing a clear MAJOR, MINOR, or PATCH recommendation based on semantic versioning rules.

How do I generate changelog release notes from git commit history?▼

Generate changelog release notes by summarizing commits and file changes between the latest git tag and HEAD, producing a structured summary ready for release documentation.

Can I run a dry run of a release without actually publishing or creating a tag?▼

Yes, you can run an offline release dry run that analyzes diffs and commits since the latest tag to preview release impact safely without creating a new tag or publishing.

Does the version bump recommendation work with any existing git tagging strategy?▼

The version bump recommendation works by scanning your existing git tags, specifically identifying the latest release tag and comparing it against HEAD to determine the necessary bump.

Related Skills

Explore More Product & Management Skills→
jk278jk278

git-analyzer

Analyze git repositories to summarize commit history and file changes.

Community
Intermediate
vfarcicvfarcic
2

dot-ai-tag-release

Create semantic version release tags from changelog.d fragments.

Community
Advanced
drgaciwdrgaciw

changelog-automation

Generate changelogs and release notes from Conventional Commits in CI/CD pipelines.

Community
Intermediate
hackurhackur
1

Release Management

Automate semantic versioning, changelog generation, and git tagging for releases.

Community
Advanced