// Dry run for release: summarize changes since last release and suggest version bump.
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.
Maps rulesync feature implementations to upstream coding-agent documentation. Use when evaluating rulesync issues, comparing any coding-agent client with rulesync source capability surfaces, checking support, or planning a client map.
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.
Draft a new release of the project.
Create a GitHub issue with detailed description, purpose, and appropriate labels
Scan for malicious code in git diff between a tag/commit and HEAD
| 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.
Get the latest release tag.
git fetch --tags to ensure all tags are available.git describe --tags --abbrev=0 to get the latest tag.Compare code changes between the latest tag and the current HEAD.
git log ${latest_tag}..HEAD --oneline to get the commit list.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:
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.