Agent skill

Release Dry Run

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

MITAuto-check passedDevelopment

Install Release Dry Run

skills CLI

$ npx skills add dyoshikawa/rulesync --skill release-dry-run -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install dyoshikawa/rulesync release-dry-run --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.rulesync/skills/release-dry-run .claude/skills/release-dry-run && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "release-dry-run" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/release-dry-run into .claude/skills/release-dry-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-dry-run", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/release-dry-run

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add dyoshikawa/rulesync --skill release-dry-run -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install dyoshikawa/rulesync release-dry-run --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.rulesync/skills/release-dry-run .agents/skills/release-dry-run && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "release-dry-run" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/release-dry-run into .agents/skills/release-dry-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-dry-run", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add dyoshikawa/rulesync --skill release-dry-run -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install dyoshikawa/rulesync release-dry-run --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.rulesync/skills/release-dry-run .cursor/skills/release-dry-run && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "release-dry-run" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/release-dry-run into .cursor/skills/release-dry-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-dry-run", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/dyoshikawa/rulesync.git --path .rulesync/skills/release-dry-run

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add dyoshikawa/rulesync --skill release-dry-run -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install dyoshikawa/rulesync release-dry-run --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.rulesync/skills/release-dry-run .gemini/skills/release-dry-run && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "release-dry-run" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/release-dry-run into .gemini/skills/release-dry-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-dry-run", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install dyoshikawa/rulesync release-dry-run

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add dyoshikawa/rulesync --skill release-dry-run -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .github/skills && cp -r skills-src/.rulesync/skills/release-dry-run .github/skills/release-dry-run && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "release-dry-run" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/release-dry-run into .github/skills/release-dry-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-dry-run", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add dyoshikawa/rulesync --skill release-dry-run -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install dyoshikawa/rulesync release-dry-run --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.rulesync/skills/release-dry-run .opencode/skills/release-dry-run && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "release-dry-run" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/release-dry-run into .opencode/skills/release-dry-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-dry-run", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: release-dry-run
GitHub stars: 1.5k
Token cost: ~657 tokens
SKILL.md length: 251 words
Files: 1
Skills in repo: 40
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

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

Works in 5 steps: Get the latest release tag. → Compare code changes between the latest… → Analyze the changes and create a summary… → …
Development work in your project
Calls git

What it does

Release Dry Run is an agent skill from dyoshikawa/rulesync. Dry run for release: summarize changes since last release and suggest version bump.

Its SKILL.md is about 660 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with Git. The repository describes itself as: A Utility CLI for AI Coding Agents. The licence is MIT.

When your agent uses it

Development work in your project

Example prompts

“/release-dry-run”

Requirements

Node.js

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

Get the latest release tag.
Compare code changes between the latest tag and the current HEAD.
Analyze the changes and create a summary in the following format
Based on the analysis, suggest the appropriate version bump following semantic versioning rules
Output the final recommendation in the following format

What it can do on your machine

Read from SKILL.md and the folder at commit 625bf98. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Release Dry Run loads about 657 tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 251 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~25
When it runs · the whole SKILL.md, loaded when a task matches: ~657

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from dyoshikawa/rulesync at commit 625bf98, republished under its MIT licence (© dyoshikawa). 251 words, ~657 tokens.

Download SKILL.mdSave it as .claude/skills/release-dry-run/SKILL.md (or your agent's skills folder).

name: release-dry-run
description: Dry run for release: summarize changes since last release and suggest version bump.
targets: *

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

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.
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.

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.)

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)
Important: Whenever the changes include any feature removal or a change in the behavior of an existing feature, do not hesitate to choose a MAJOR version bump. Prioritize protecting users from unexpected breakage over keeping the version number low.

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.

Files

Just SKILL.md in .rulesync/skills/release-dry-run of dyoshikawa/rulesync.

Open the folder on GitHubat commit 625bf98

Compare with similar skills

Release Dry Run next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Release Dry Run compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Release Dry Run this skilldyoshikawa/rulesync	1.5k	—	~657	Automated safety check: Pass	MIT	yesterday
Finishing a Development Branchobra/superpowers	297k	5 repos	~1.9k	Automated safety check: Pass	MIT	today
Code Review ChecklistshareAI-lab/learn-claude-code	78k	4 repos	~1.1k	Automated safety check: Pass	MIT	12 days ago
Code Design Rationale Investigatorcursor/plugins	11k	9 repos	~2.6k	Automated safety check: Pass	None	today
Contributor-First PR MergeHKUDS/OpenHarness	16k	1 repos	~847	Automated safety check: Pass	MIT	4 mo ago
Finishing A Development Branchfarm-fe/farm	5.6k	34 repos	~1.8k	Automated safety check: Pass	MIT	18 days ago

Similar skills

Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
297k GitHub starsUsed in 5 repos~1.9k tokens
DevelopmentAuto-check passed
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
78k GitHub starsUsed in 4 repos~1.1k tokens
DevelopmentAuto-check passed
Code Design Rationale Investigator
cursor/plugins
Official
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
11k GitHub starsUsed in 9 repos~2.6k tokens
DevelopmentAuto-check passed
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
16k GitHub starsUsed in 1 repo~847 tokens
DevelopmentAuto-check passed
Finishing A Development Branch
farm-fe/farm
A skill your agent uses when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for…
5.6k GitHub starsUsed in 34 repos~1.8k tokens
DevelopmentAuto-check passed
Migrate Internal Package into Ghost
TryGhost/Ghost
Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.
56k GitHub stars~3.8k tokensUpdated today
DevelopmentAuto-check passed

More from dyoshikawa/rulesync

All 40 skills in this repo

Rulesync Feature Research
dyoshikawa/rulesync
Maps rulesync feature implementations to upstream coding-agent documentation.
1.5k GitHub stars~1.8k tokensUpdated yesterday
Auto-check passed
Babysit Dependabot PR
dyoshikawa/rulesync
Babysit a Dependabot dependency-bump PR all the way to merge: verify the author is the genuine Dependabot bot, diagnose and resolve any CI failure (excluding or fixing a breaking bump when needed)…
1.5k GitHub stars~1.3k tokensUpdated yesterday
Auto-check passed
Commit Push PR
dyoshikawa/rulesync
Commit current changes, push to remote, and create or update a pull request.
1.5k GitHub stars~458 tokensUpdated yesterday
Auto-check passed
Git Worktree Runner
dyoshikawa/rulesync
Manages git worktrees using git-worktree-runner (gtr). An agent skill from dyoshikawa/rulesync.
1.5k GitHub stars~1.3k tokensUpdated yesterday
Auto-check: notes
Goal PR
dyoshikawa/rulesync
Drive a pull request to a clean state and merge it: run the review-pr skill, fix every mid-or-above finding, and repeat until no mid-or-above findings remain, then merge.
1.5k GitHub stars~1.4k tokensUpdated yesterday
Auto-check passed
Goal Release
dyoshikawa/rulesync
Cut a release end to end: use the draft-release skill to open the release PR and draft GitHub release, wait for CI to turn green, run the merge-pr skill to merge the release PR, then update the…
1.5k GitHub stars~2k tokensUpdated yesterday
Auto-check passed

Works with

Questions about Release Dry Run

What does Release Dry Run do?

Dry run for release: summarize changes since last release and suggest version bump. Release Dry Run is an agent skill from dyoshikawa/rulesync. Dry run for release: summarize changes since last release and suggest version bump.

When should I use Release Dry Run?

Release Dry Run fits situations like: development work in your project.

How do I install Release Dry Run in Claude Code?

Run `npx skills add dyoshikawa/rulesync --skill release-dry-run -a claude-code`. Or copy the skill folder (.rulesync/skills/release-dry-run in dyoshikawa/rulesync) into .claude/skills/release-dry-run in your project. Claude Code loads it when a task matches its description.

How do I install Release Dry Run in Codex?

Run `npx skills add dyoshikawa/rulesync --skill release-dry-run -a codex`. Or copy the skill folder (.rulesync/skills/release-dry-run in dyoshikawa/rulesync) into .agents/skills/release-dry-run in your project. Codex loads it when a task matches its description.

Can I use Release Dry Run in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dyoshikawa/rulesync --skill release-dry-run -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-dry-run, .gemini/skills/release-dry-run, .github/skills/release-dry-run and .opencode/skills/release-dry-run in your project.

What does Release Dry Run need to run?

Going by SKILL.md and its folder, Release Dry Run needs the command-line tools its instructions call (git). Our summary lists: Node.js.

Does Release Dry Run access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Release Dry Run safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Release Dry Run use?

Release Dry Run is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Release Dry Run use?

About 657 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Release Dry Run?

Skills that share tags, products or a category with Release Dry Run: Finishing a Development Branch (obra/superpowers, 297k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Code Design Rationale Investigator (cursor/plugins, 11k stars) and Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Dry Run?

dyoshikawa (a GitHub user) maintains it in dyoshikawa/rulesync, which has 1,509 GitHub stars. The repository holds 40 skills in this directory. The repository was last updated on October 9, 2026.

Source: dyoshikawa/rulesync on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Release Dry Run

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Steps

Files

Compare with similar skills

Similar skills

More from dyoshikawa/rulesync

Related

Questions about Release Dry Run