Automate software releases with version bumping, changelog generation, and GitHub releases.
npx skills add https://github.com/lklimek/memcan --skill release-lklimek
Please help me install this Agent Skill. Skill: release Source: https://github.com/lklimek/memcan/tree/main/.claude/skills/release Command: npx skills add https://github.com/lklimek/memcan --skill release-lklimek
This Skill streamlines the complex and error-prone process of releasing new software versions, ensuring consistency and reducing manual effort.
Run the release skill to automatically determine the next version and create a new release.
High-intent search queries and answers about installing and using this skill.
Automated software release tools analyze git history and code diffs to determine SemVer increments, generate Keep a Changelog formatted notes, commit changes, and push to GitHub. This streamlines the entire release process by evaluating commit history to decide whether a major, minor, or patch version bump is required.
Yes, automating version management and publishing requires git, GitHub CLI, and Cargo. GitHub CLI is needed to create the GitHub release, while Cargo handles the version management and publishing aspects for your software project.
Automated changelog generation works by analyzing git history and code diffs to produce human-readable release notes. It formats the extracted commit history according to Keep a Changelog standards, ensuring consistent documentation of code changes for each new software version.
Yes, you can automatically create GitHub releases from commit history. The automation analyzes your code diffs to determine version increments, generates the changelog, commits the version update, pushes to the remote repository, and publishes the GitHub release without manual intervention.
The best way to determine SemVer increments from git history is by analyzing code diffs and commit messages. This automated approach evaluates the impact of changes to accurately decide whether a major, minor, or patch version bump is appropriate for the next release.
Using Cargo for automated version management and publishing limits the workflow to projects within the Rust ecosystem. The release automation requires Cargo specifically for version management, meaning it is not directly applicable to software projects built with other package managers.
lanejAutomates Git and GitHub workflows including commits, branches, pull requests, and gh CLI tasks.
huyhung9630Guide software release preparation, versioning, and execution with confirmation.
l3ochoParse Conventional Commits and Keep a Changelog formats to generate release notes.
figuedmundoAutomate changelog generation and release management with Conventional Commits.
