release

Automating version bumping and changelog generation for a CLI package involves analyzing project commits to apply semantic version increments and automatically generating an updated changelog. This skill handles these tasks by reading project files and triggering based on release-specific keywords.

Preparing release notes from commit history is best handled by automatically aggregating commits and tags to create a structured GitHub release body. This skill analyzes your project's version history to compile these notes and provides a step-by-step publishing workflow.

This release management workflow does not require external dependencies to function. It operates using internal scripts and directly accesses your project files to perform commit analysis, version bumping, and changelog generation.

Yes, you can use semantic versioning triggers to automate your CLI package release process. The skill specifically monitors for these semver triggers and release-specific keywords to automatically initiate version increments and changelog updates.

Determining semantic version increments through commit analysis works by scanning your project's commit history to identify the nature of changes. The skill uses this analysis to automatically apply the correct semver version bump and prepare the corresponding release notes.

Using scripts for release management automation requires granting access to your project files for analysis and modification. The process is currently tailored specifically for CLI packages and depends on recognizing semantic versioning triggers or release keywords to execute accurately.