release-dry-run

Dry run for release: summarize changes since last release and suggest version bump.

986 stars

Best use case

release-dry-run is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Dry run for release: summarize changes since last release and suggest version bump.

Teams using release-dry-run should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/release-dry-run/SKILL.md --create-dirs "https://raw.githubusercontent.com/dyoshikawa/rulesync/main/.rulesync/skills/release-dry-run/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/release-dry-run/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How release-dry-run Compares

Feature / Agentrelease-dry-runStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Dry run for release: summarize changes since last release and suggest version bump.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

This is a dry run command for release. It will summarize the changes since the last release and suggest the appropriate version bump based on semantic versioning.

## Steps

1. Get the latest release tag.
   - Run `git fetch --tags` to ensure all tags are available.
   - Run `git describe --tags --abbrev=0` to get the latest tag.
   - Assign the result to $latest_tag.

2. Compare code changes between the latest tag and the current HEAD.
   - Run `git log ${latest_tag}..HEAD --oneline` to get the commit list.
   - Run `git diff ${latest_tag}..HEAD --stat` to get the file change statistics.

3. Analyze the changes and create a summary in the following format:

   ```
   ## Changes Summary

   ### Commits since ${latest_tag}
   - List of commits with their messages

   ### Changed Files
   - Summary of file changes (added, modified, deleted)

   ### Change Categories
   - **Breaking Changes**: List any breaking changes (API changes, removed features, etc.)
   - **New Features**: List new features added
   - **Bug Fixes**: List bug fixes
   - **Other Changes**: List other changes (refactoring, documentation, tests, etc.)
   ```

4. Based on the analysis, suggest the appropriate version bump following semantic versioning rules:
   - **MAJOR** (X.0.0): Breaking changes that are not backward compatible
     - Removed or renamed public APIs
     - Changed behavior of existing features
     - Dropped support for older Node.js versions
   - **MINOR** (x.Y.0): New features that are backward compatible
     - New CLI commands or options
     - New configuration options
     - New tool support
   - **PATCH** (x.y.Z): Bug fixes and minor improvements
     - Bug fixes
     - Documentation updates
     - Internal refactoring without API changes
     - Dependency updates (unless they cause breaking changes)

5. Output the final recommendation in the following format:

   ```
   ## Version Bump Recommendation

   Current version: ${latest_tag}
   Recommended bump: MAJOR / MINOR / PATCH
   Suggested new version: vX.Y.Z

   ### Reasoning
   - Explain why this version bump is recommended based on the changes.
   ```

**Note**: This is a dry run only. No files will be modified and no commits will be made.

Related Skills

draft-release

986
from dyoshikawa/rulesync

Draft a new release of the project.

rulesync

986
from dyoshikawa/rulesync

Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.

skill-creator

986
from dyoshikawa/rulesync

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

security-scan-diff

986
from dyoshikawa/rulesync

Scan for malicious code in git diff between a tag/commit and HEAD

playwright-cli

986
from dyoshikawa/rulesync

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

git-worktree-runner

986
from dyoshikawa/rulesync

Manages git worktrees using git-worktree-runner (gtr). Use when the user needs to create, list, remove, or navigate worktrees with `git gtr` commands, open editors or AI tools in worktrees, manage parallel development branches, or check out GitHub PRs (including from forks) into worktrees.

create-scrap-issue

986
from dyoshikawa/rulesync

Create a GitHub issue that consolidates passed content into a single scrap issue with background context and solution details, labeled as maintainer-scrap. Use when the user wants to create a scrap issue, jot down notes as a GitHub issue, or save findings for later.

create-issue

986
from dyoshikawa/rulesync

Create a GitHub issue with detailed description, purpose, and appropriate labels

review-pr

971
from dyoshikawa/rulesync

Review a pull request for code quality and security issues. Use when the user wants to review a PR, check PR code changes, or audit a pull request. Triggers on: "review PR", "review pull request", "check this PR", "/review-pr".

review-and-comments

971
from dyoshikawa/rulesync

Review a PR for code quality and security issues, then post review comments on it. Runs review-pr followed by post-review-comments sequentially.

rebase-latest-main

971
from dyoshikawa/rulesync

Fetch latest origin/main and rebase it onto the current branch, resolving conflicts if necessary. Use when the user wants to rebase on main, update their branch with latest main, or sync with upstream.

post-review-comments

971
from dyoshikawa/rulesync

Post line-level review comments and an overall review comment on a PR in English with a natural, concise writing style