create-github-release

To automate a GitHub release from a semantic version input, the skill computes diffs from the previous release, prepares release notes, builds a Windows ZIP artifact, and determines draft or prerelease status before publishing.

Release note generation for automated GitHub releases works by fetching previous release boundaries and analyzing commit diffs to automatically collect and assemble changes for the new version.

Yes, you need to manually confirm before publishing a GitHub release because the workflow enforces safety checks and explicitly prompts for user approval during final execution.

Yes, you can build a Windows ZIP artifact and attach it to a GitHub prerelease, as the workflow handles asset packaging and automatically assigns tag and release naming for draft or prerelease statuses.

The best way to verify tags and compute diffs for GitHub versioning is using helper scripts that fetch release boundaries, validate existing tags, and collect changes between the previous release and the new semantic version.

An automated GitHub release should be marked as a draft or prerelease when the workflow determines the new version requires staged validation, automatically setting the status while attaching the build ZIP asset.