Menü
Dry run for release: summarize changes since last release and suggest version bump.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Approve a pull request using gh pr review --approve
Batch-triage open pull requests: list PRs with prs-awaiting-maintainer, review each with review-pr, then post-review-comments when there are merge-blocker findings, or create-scrap-issue for non-blocking findings and merge-pr when there are none. Use when the user wants to review and resolve a batch of PRs in one pass.
Clean up unnecessary local branches and prune stale remote-tracking branches
Clean git worktrees created by git-worktree-runner
Commit current changes, push to remote, and create or update a pull request. Use when the user wants to commit and create a PR, push changes and open a pull request, or ship their current work as a PR.
Analyze the differences between the current branch and origin/main, and summarize the current work progress
| name | release-dry-run |
| description | Dry run for release: summarize changes since last release and suggest version bump. |
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:
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.