workclaw-release-prep

To generate bilingual release notes from git commits, the skill analyzes recent git history, tags, and project manifests to draft concise user-visible summaries in both Chinese and English, ready for human review.

Determining the next version number for a software release involves analyzing recent git commits and tags to recommend a patch, minor, or major version bump with clear rationale based on the detected changes.

To prepare a desktop release with automated versioning, you need access to git history, project manifest files, configuration files, and the last git tag to ensure all impactful changes are captured.

Yes, you can automate release scope inspection for project manifests. The skill reviews relevant manifests, configuration files, and documentation to ensure all user-visible changes are captured before drafting notes.

You should use automated bilingual release notes over manual drafting during release preparation when you need to save time and reduce errors in summarizing git history into Chinese and English user-facing changes.