Individual skill
release-dry-run
Dry run for release: summarize changes since last release and suggest version bump.
.rulesync/skills/release-dry-run/SKILL.md
Source commit 2d5bbc81aa01346601fcb2d1e18c71af07a02728
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,590
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,628 bytes
Read excerpt
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: