release-har_skill

Overview

This skill automates universal release tasks across projects: version determination, changelog updates, file version bumps, git commits, tags, pushes, and optional GitHub Releases. It supports semantic versioning and common file types (package.json, pyproject.toml, Cargo.toml, VERSION). Use it to reduce manual steps and ensure consistent, repeatable releases.

How this skill works

The skill inspects the repository state (uncommitted changes, diffs, recent commits, existing tags) and asks for the next version or takes a semantic increment (patch/minor/major). It updates changelogs if present, edits applicable version files, stages and commits changes, creates annotated git tags, pushes branch and tag, and can create a GitHub Release with assembled release notes. A --dry-run option previews actions without executing them.

When to use it

• When you need to bump a project version (patch/minor/major) and create a git tag.
• When preparing a release and you want changelog and version files updated consistently.
• When you want to push a release tag and optionally create a GitHub Release.
• When you want an automated, repeatable release flow across multiple language projects.
• When you need a dry-run preview to validate release steps before execution.

Best practices

• Ensure the working tree is clean before starting to avoid unintended changes.
• Run the skill with --dry-run first to verify the computed version and file changes.
• Update or maintain CHANGELOG.md entries before or during the release step for clear release notes.
• Confirm the chosen version (prompted by the skill) to avoid accidental major bumps.
• Use branch protection and CI checks before pushing release tags to main branches.

Example use cases

• Bump a Node.js package patch version, update package.json, commit, tag vX.Y.Z, and push.
• Perform a minor release for a Python project by editing pyproject.toml and creating a GitHub Release.
• Create a release for a Rust crate by updating Cargo.toml, tagging, and pushing the release tag.
• Preview a release with --dry-run to inspect changes before committing and tagging.
• Generate release notes from recent commits and publish a GitHub Release with the assembled notes.