Bump project versions, finalize CHANGELOGs, and create GitHub releases.
npx skills add https://github.com/rodacato/kwik-e-dev --skill ship-rodacato
Please help me install this Agent Skill. Skill: ship Source: https://github.com/rodacato/kwik-e-dev/tree/main/plugins/lifecycle/skills/ship Command: npx skills add https://github.com/rodacato/kwik-e-dev --skill ship-rodacato
This skill automates the release process by bumping versions, finalizing the CHANGELOG, tagging the release, pushing changes, and creating a GitHub release. It reads docs/guides/releasing.md if present and follows it; otherwise it falls back to Keep-a-Changelog + SemVer defaults. It is not meant for setting up the release process itself — that is handled by launchpad:releasing.
Initiate a release by instructing the agent to cut a new release (e.g., "ship 0.1.2" or "release this"), triggering version bumps, changelog finalization, tagging, and GitHub release creation.
High-intent search queries and answers about installing and using this skill.
Automate GitHub releases by bumping project versions, finalizing the CHANGELOG Unreleased section, tagging commits, and creating the GitHub release. The workflow reads a custom release guide if present or defaults to Keep-a-Changelog and SemVer conventions.
Bump SemVer versions reproducibly by applying deterministic release steps that check the current version, finalize changelog entries, tag the commit, and push changes to GitHub. It follows standard Keep-a-Changelog conventions unless a custom releasing guide overrides the defaults.
Yes, you can use a custom releasing guide. The automation reads docs/guides/releasing.md if present and follows its instructions for versioning and tagging, defaulting to Keep-a-Changelog and SemVer standards only when no guide is available.
Yes, an Unreleased section in the CHANGELOG is required. The release automation reads this section to finalize release notes, bumping the project version and moving entries under the newly created version tag before publishing to GitHub.
A release guide is not strictly required. The automation defaults to Keep-a-Changelog and SemVer conventions when docs/guides/releasing.md is absent, ensuring deterministic and auditable version checks, changelog management, tagging, commits, and GitHub release creation.
No, this workflow handles cutting reproducible releases, not setting up the initial release process. It bumps versions, finalizes changelogs, tags, and creates GitHub releases, relying on existing setup configurations rather than establishing them.
deinsoftwareBump SWPM versions in package.json and update CHANGELOG.md from commits.
ushironokoAutomate version bumps, git tagging, and crates.io publishing for Rust projects.
Fantasia1999Generate changelog entries from Conventional Commits in Markdown or JSON formats.
linenoizeGenerate conventional git commits, branch names, and pull request descriptions.
