release-dry-run
Dry run for release: summarize changes since last release and suggest version bump.
Profile →npx skills add dyoshikawa/rulesync --skill release-dry-run --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
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.
- Steps
What does the release-dry-run skill do?
Dry run for release: summarize changes since last release and suggest version bump.
How do I install it?
Run `npx skills add dyoshikawa/rulesync --skill release-dry-run --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From dyoshikawa/rulesync, a repository with 1,285 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.